AI Assist can send a key to another endpoint and has no budget; MCP unpublish needs no dry run
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with AiClientFactory.cs and AiAssistService.cs for endpoint binding and rate limiting, then inspect McpContentTools.cs and docs/planning/specification/09-ai-agents.md for unpublish dry runs. Trace how AiUsage is stored and queried before choosing where to enforce a per-site daily budget. Done means all four acceptance checks pass, with tests for each; the issue names no test files.
Written by the indexing model from the issue text.
Description
Problem
- An AI key set by the operator can be sent to another allowed endpoint.
src/plugins/FluentCMS.Plugins.AiAssist/AiClientFactory.cs:58-77binds the OpenAI configuration key to its own endpoint, but notFluentCms:Ai:AzureOpenAi:ApiKeyorOpenAiCompatible:ApiKey(:65). A site admin can point the site at any other entry ofAllowedEndpointsand the key goes there. - The rate limit is taken after the local work.
AiAssistService.cs:185,199,213,216: the draft read, the image decode and resize for alt text, and client creation all run before the bucket is consumed. - There is no cost budget. Limits today are
CallsPerMinutein memory,MaxInputLength,MaxOutputTokensandRequestTimeout. Token usage is recorded inAiUsagefor 90 days and never enforced. - MCP
unpublishtakes live content down without a confirmed dry run.src/plugins/FluentCMS.Plugins.Mcp/McpContentTools.cs:429-451call the content service directly, while{type}_deleteandbulkgo throughMcpDryRuns(:141,:499).docs/planning/specification/09-ai-agents.md:14asks for dry runs on delete and bulk only.
Proposal
- Apply the own-endpoint rule to the configuration key of every provider.
- Check the bucket after the permission checks and consume it just before sending.
- Add a daily token budget per site (off by default), summed from
AiUsagebefore a call. - Route
unpublishthrough the dry-run plan and token;publishstays direct. Update the specification line.
Acceptance
- A configuration key is never sent to an endpoint other than the one it was configured for
- A caller over the limit is refused before the draft is read or an image decoded
- A site over its daily budget is refused with a problem that says when it resets
- MCP
unpublishwithout a valid confirmation token returns the plan and changes nothing - Tests for each
Found in the code review of 17 Nov 2026.
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100