AI agents use update_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.
This tool creates or modifies data reversibly—it updates existing product fields without deleting or destroying data. While it could affect business operations (e.g., changing prices, descriptions, stock flags), the changes are not irreversible and can be corrected. The severity is medium because misuse could impact product catalog accuracy and customer-facing information, but the effects remain correctable.
From the tool's definition Tool description states 'Update one or more fields on an existing product.' The verb 'update' and the context of modifying product data in a CRM system indicate reversible modification.
Attacks that exploit this kind of access
Update one or more fields on an existing product. 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 update_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.
update_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 update_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 update_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.
update_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 →