AI agents use rh11_projects_archive 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.
Although the tool performs a deletion operation, it is explicitly a soft delete that can be undone by recreating the project. This makes it a reversible data modification (Write) rather than irreversible (Destructive). The blast radius is medium because archiving a project could disrupt active workflows and schedules, but the operation is recoverable.
From the tool's definition 'Archive (soft delete)' indicates a reversible modification to project state; the description explicitly states 'The project can be reactivated by creating a new project with the same ASIN+keyword+region', confirming the action is not permanent.
Attacks that exploit this kind of access
Archive (soft delete) a Rhodium11 Amazon project. The project can be reactivated by creating a new project with the same ASIN+keyword+region. 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_projects_archive: 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_projects_archive 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_projects_archive 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_projects_archive. 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_projects_archive 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 →