AI agents use rh11_feedback_submit to create or update resources in Rhodium11 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rhodium11 environment.
This tool creates new feedback entries in the system, which is a reversible write operation. The severity is low because feedback submission has minimal blast radius—it cannot delete data, trigger financial transactions, or execute arbitrary code. An AI agent misusing this tool could at worst spam feedback, but the duplicate rejection mechanism provides some protection.
From the tool's definition Tool submits feedback (writes data) with character limit 10-5000 characters. Description indicates creation of new feedback records without data deletion or financial impact.
Attacks that exploit this kind of access
Submit feedback to Rhodium11 (10-5000 characters). Do not submit duplicate feedback — identical text will be rejected. It is categorised as a Write tool in the Rhodium11 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rhodium11 MCP server in PolicyLayer and add a rule for rh11_feedback_submit: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rhodium11. Nothing to install.
rh11_feedback_submit 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 rh11_feedback_submit rule in your PolicyLayer 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 PolicyLayer policy for rh11_feedback_submit. 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.
rh11_feedback_submit is provided by the Rhodium11 MCP server (rhodium11/rhodium11-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →