Store uploaded files. Receives file objects with name, size, type, data (base64).
AI agents use store_files to create or update resources in Cryptosense — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cryptosense environment.
This tool writes data by storing uploaded files on the server. It creates new data (file storage) which is reversible/manageable, placing it in the Write category. The severity is medium because storing arbitrary base64-encoded files could be misused to upload malicious content, but it does not inherently execute or delete data.
From the tool's definition Store uploaded files. Receives file objects with name, size, type, data (base64).
Attacks that exploit this kind of access
Store uploaded files. Receives file objects with name, size, type, data (base64). It is categorised as a Write tool in the Cryptosense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cryptosense MCP server in PolicyLayer and add a rule for store_files: 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 Cryptosense. Nothing to install.
store_files 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 store_files 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 store_files. 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.
store_files is provided by the Cryptosense MCP server (josephibra/cryptosense-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 →