rename_record · Devon MCP: Risk & Policy

WHAT IT DOES

What rename_record does on Devon

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

WHY IT NEEDS A POLICY

Why rename_record needs a policy

Renaming a record modifies its metadata in a reversible manner. This is a Write operation because it updates data without irreversibly deleting or destroying it. The change can be undone by renaming again. Severity is medium because unintended renames could cause confusion in document organization and workflows, but the impact is limited in scope and easily correctable.

From the tool's definition Tool description: 'Renames a specific record in DEVONthink.' The verb 'renames' indicates a modification operation that changes metadata of an existing record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_record Rate-limited

rename_record 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_record": {
      "limits": [
        {
          "counter": "rename_record_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 Devon, so you can run agents against it safely.

FAQ

Questions about rename_record

What does the rename_record tool do? +

Renames a specific record in DEVONthink. It is categorised as a Write tool in the Devon 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_record? +

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

What risk level is rename_record? +

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

Can I rate-limit rename_record? +

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

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

rename_record is provided by the Devon MCP server (mnott/devon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.