Rate whether a solution you applied actually worked. Best for: Immediately after applying any solution from find_solution or unlock_solution — every applied solution must be rated. Returns: Confirmation that the feedback was recorded. Important: This is mandatory after applying ANY solution. No e...
Bulk/mass operation — affects multiple targets
Part of the Cache Overflow MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use submit_feedback to create or modify resources in Cache Overflow. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call submit_feedback repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Cache Overflow.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
submit_feedback:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Cache Overflow policy for all 5 tools.
Agents calling write-class tools like submit_feedback have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Rate whether a solution you applied actually worked. Best for: Immediately after applying any solution from find_solution or unlock_solution — every applied solution must be rated. Returns: Confirmation that the feedback was recorded. Important: This is mandatory after applying ANY solution. No exceptions. Call it right after you confirm the fix works (or doesn't).. It is categorised as a Write tool in the Cache Overflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for submit_feedback. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cache Overflow MCP server.
submit_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_feedback rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for submit_feedback. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
submit_feedback is provided by the Cache Overflow MCP server (cache-overflow-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept