upload_file · MCP Developer Server MCP: Risk & Policy

WHAT IT DOES

What upload_file does on MCP Developer Server

AI agents use upload_file to create or update resources in MCP Developer Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Developer Server environment.

WHY IT NEEDS A POLICY

Why upload_file needs a policy

The upload_file tool is classified as Write because it creates new file objects in the shared workspace. While upload operations are typically reversible (files can be deleted), the high severity accounts for the potential to upload malicious code, overwrite critical files, or pollute the shared workspace used by other operations.

From the tool's definition Tool description states 'Upload a file to the shared workspace', which creates or modifies data in the shared workspace by adding a new file. The context of isolated Docker containers suggests files are persisted within the environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_file Rate-limited

upload_file 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": {
    "upload_file": {
      "limits": [
        {
          "counter": "upload_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about upload_file

What does the upload_file tool do? +

Upload a file to the shared workspace. It is categorised as a Write tool in the MCP Developer Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_file? +

Register the MCP Developer Server 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 MCP Developer Server. Nothing to install.

What risk level is upload_file? +

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

Can I rate-limit upload_file? +

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.

How do I block upload_file completely? +

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.

What MCP server provides upload_file? +

upload_file is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.