store_files

Store uploaded files. Receives file objects with name, size, type, data (base64).

SERVERCryptosense SOURCEjosephibra/cryptosense-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/josephibra-cryptosense-mcp/store-files.md

WHAT IT DOES

What store_files does on Cryptosense

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.

RISK

Why store_files is rated Medium

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

RECOMMENDED RULE

The rule that runs store_files safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cryptosense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store_files, this is the rule to start with:

store_files Rate-limited

store_files stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "store_files": {
      "limits": [
        {
          "counter": "store_files_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cryptosense, apply this rule, and every store_files call is checked against it from then on.

FAQ

Questions about store_files

What does the store_files tool do? +

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.

How do I enforce a policy on store_files? +

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.

What risk level is store_files? +

store_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit store_files? +

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.

How do I block store_files completely? +

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.

What MCP server provides store_files? +

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.

KEEP EXPLORING

More on Cryptosense, and thousands of servers like it.

This server

All 36 Cryptosense tools →

Across the catalogue

scaffold_project_files on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →