rename_folder · Dynalist MCP: Risk & Policy

WHAT IT DOES

What rename_folder does on Dynalist

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

WHY IT NEEDS A POLICY

Why rename_folder needs a policy

Renaming a folder modifies metadata reversibly and does not destroy data or execute arbitrary code. This is a typical Write operation. Severity is medium because folder renames could affect document organization and access patterns, but the change is easily undoable.

From the tool's definition Tool name 'rename_folder' indicates modification of folder metadata. Sibling tools include 'create_folder' and 'delete_items', establishing this as a document organization/management server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_folder Rate-limited

rename_folder 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_folder": {
      "limits": [
        {
          "counter": "rename_folder_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 Dynalist, so you can run agents against it safely.

FAQ

Questions about rename_folder

What does the rename_folder tool do? +

${INSTRUCTIONS_FIRST_GUIDANCE}. It is categorised as a Write tool in the Dynalist 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_folder? +

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

What risk level is rename_folder? +

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

Can I rate-limit rename_folder? +

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

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

rename_folder is provided by the Dynalist MCP server (wawworld/dynalist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.