AI agents use upload_file 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.
The tool creates new data (file upload) in the keyCRM system, making it a Write operation. Severity is medium because uploaded files could contain malicious content, occupy storage quota, or be used to exfiltrate data later, but the immediate effect is reversible (files can typically be deleted).
From the tool's definition Tool description states 'Upload a file to keyCRM Storage', which creates a new file resource and returns a file_id. This is a create/write operation that modifies the storage system.
Attacks that exploit this kind of access
Upload a file to keyCRM Storage from a publicly accessible URL. Returns a file_id. 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 upload_file: 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.
upload_file 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 upload_file 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 upload_file. 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.
upload_file 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 →