upload_local_file · Yadisk MCP: Risk & Policy

WHAT IT DOES

What upload_local_file does on Yadisk

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

WHY IT NEEDS A POLICY

Why upload_local_file needs a policy

The tool uploads local files to Yandex Disk, which creates new data in the cloud storage system. This is a Write operation (reversible via delete), not Destructive since uploads don't irreversibly overwrite existing critical data by design.

From the tool's definition Tool name 'upload_local_file' and server description indicating 'upload/download' capabilities; server context shows this is a Yandex Disk file management tool that creates new files in cloud storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_local_file Rate-limited

upload_local_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_local_file": {
      "limits": [
        {
          "counter": "upload_local_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 Yadisk, so you can run agents against it safely.

FAQ

Questions about upload_local_file

What does the upload_local_file tool do? +

upload_local_file. It is categorised as a Write tool in the Yadisk 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_local_file? +

Register the Yadisk MCP server in PolicyLayer and add a rule for upload_local_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 Yadisk. Nothing to install.

What risk level is upload_local_file? +

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

Can I rate-limit upload_local_file? +

Yes. Add a rate_limit block to the upload_local_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_local_file completely? +

Set action: deny in the PolicyLayer policy for upload_local_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_local_file? +

upload_local_file is provided by the Yadisk MCP server (patr56/yadisk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.