Medium Risk

store_file

Upload or overwrite a file. Content should be base64-encoded for binary, or plain text (which will be base64-encoded automatically).

Accepts raw HTML/template content (content)

Part of the KeyID MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@keyid/agent-kit Write Risk 2/5

AI agents use store_file to create or modify resources in KeyID. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call store_file repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach KeyID.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

keyid.yaml
tools:
  store_file:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full KeyID policy for all 64 tools.

Tool Name store_file
Category Write
MCP Server KeyID MCP Server
Risk Level Medium

View all 64 tools →

Agents calling write-class tools like store_file have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the store_file tool do? +

Upload or overwrite a file. Content should be base64-encoded for binary, or plain text (which will be base64-encoded automatically).. It is categorised as a Write tool in the KeyID 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_file? +

Add a rule in your Intercept YAML policy under the tools section for store_file. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the KeyID MCP server.

What risk level is store_file? +

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

Can I rate-limit store_file? +

Yes. Add a rate_limit block to the store_file rule in your Intercept 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_file completely? +

Set action: deny in the Intercept policy for store_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.

What MCP server provides store_file? +

store_file is provided by the KeyID MCP server (@keyid/agent-kit). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on KeyID

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.