rename · Yadisk MCP: Risk & Policy

WHAT IT DOES

What rename does on Yadisk

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

Renaming is a reversible modification operation that changes resource metadata without deleting data or executing code. It fits the Write category (creates or modifies data reversibly). Severity is medium because an AI agent could rename critical files to confusing names, disrupting workflows, but the operation is reversible via another rename operation.

From the tool's definition Tool description explicitly states 'Rename a file or folder', which modifies metadata/name of existing resources. The clarification '(moves it within the same directory)' confirms it alters the file system state reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename Rate-limited

rename 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": {
    "rename": {
      "limits": [
        {
          "counter": "rename_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 rename

What does the rename tool do? +

Rename a file or folder (moves it within the same directory). 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 rename? +

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

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

Can I rate-limit rename? +

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

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

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