upload_local_file_background · Yadisk MCP: Risk & Policy

WHAT IT DOES

What upload_local_file_background does on Yadisk

AI agents use upload_local_file_background 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_background needs a policy

This tool creates or modifies data (uploads files to cloud storage) reversibly—uploaded files can be deleted. It is a Write operation. Severity is medium because while file uploads can consume storage quota and potentially interfere with disk operations, they are not destructive (reversible), do not execute arbitrary code, and do not involve financial transactions.

From the tool's definition Tool name 'upload_local_file_background' combined with server description stating it 'enables file and folder management, upload/download' indicates this tool uploads files to Yandex Disk. No description provided for the tool itself.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_local_file_background Rate-limited

upload_local_file_background 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_background": {
      "limits": [
        {
          "counter": "upload_local_file_background_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_background

What does the upload_local_file_background tool do? +

upload_local_file_background. 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_background? +

Register the Yadisk MCP server in PolicyLayer and add a rule for upload_local_file_background: 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_background? +

upload_local_file_background 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_background? +

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

Set action: deny in the PolicyLayer policy for upload_local_file_background. 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_background? +

upload_local_file_background 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.