AI agents use rh11_orders_report_issue 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 issue report records attached to orders, which is a reversible write operation. While it modifies data (adding an issue report), the reports can typically be viewed, updated, or dismissed, making it Write rather than Destructive.
From the tool's definition Tool name 'rh11_orders_report_issue' and description 'Report an issue with a Rhodium11 order' indicate the tool creates or modifies state by submitting an issue report against an order.
Attacks that exploit this kind of access
Report an issue with a Rhodium11 order. Maximum 5 issue reports per order — do not retry if you receive a limit error. Description must be 1-1000 characters. 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_orders_report_issue: 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_orders_report_issue 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_orders_report_issue 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_orders_report_issue. 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_orders_report_issue 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 →