coda_rename_page · Coda MCP Server MCP: Risk & Policy

WHAT IT DOES

What coda_rename_page does on Coda MCP Server

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

WHY IT NEEDS A POLICY

Why coda_rename_page needs a policy

Renaming a page modifies metadata reversibly without deleting or destroying data. It is not a Read operation (it changes state), not Execute (no code/command execution), not Destructive (renaming is undoable), and not Financial. Write is the appropriate category. Severity is medium because an agent could rename many pages and cause organizational confusion, but the damage is easily reversible.

From the tool's definition Tool name 'coda_rename_page' and description 'Renomme une page existante' (renames an existing page) indicate modification of page metadata. This is a reversible change to page properties.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

coda_rename_page Rate-limited

coda_rename_page 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": {
    "coda_rename_page": {
      "limits": [
        {
          "counter": "coda_rename_page_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 Coda MCP Server, so you can run agents against it safely.

FAQ

Questions about coda_rename_page

What does the coda_rename_page tool do? +

Renomme une page existante. Raccourci explicite pour changer uniquement le nom. It is categorised as a Write tool in the Coda MCP 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 coda_rename_page? +

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

What risk level is coda_rename_page? +

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

Can I rate-limit coda_rename_page? +

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

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

coda_rename_page is provided by the Coda MCP Server MCP server (thierryvm/coda-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.