AI agents use archive_product to create or update resources in Keycrm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keycrm environment.
Archiving is a state modification that changes product visibility/availability in the catalogue, but the description confirms it is reversible (products can be unarchived). This qualifies as Write rather than Destructive since the operation is not permanent and data remains recoverable.
From the tool's definition Tool description explicitly states 'Archive a product. Reversible — archived products can be unarchived at any time.' Archiving modifies product state but can be undone.
Attacks that exploit this kind of access
Archive a product. Reversible — archived products can be unarchived at any time. It is categorised as a Write tool in the Keycrm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keycrm MCP server in PolicyLayer and add a rule for archive_product: 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 Keycrm. Nothing to install.
archive_product 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 archive_product 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 archive_product. 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.
archive_product is provided by the Keycrm MCP server (ivanklymenko/keycrm-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 →