duplicate_record · Devon MCP: Risk & Policy

WHAT IT DOES

What duplicate_record does on Devon

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

Duplicating a record creates a new copy in a destination group — this is a reversible write operation (the duplicate can be deleted later). It does not delete or overwrite data, execute code, or move money. The blast radius is medium because an agent could flood a database with many duplicate records across groups.

From the tool's definition Duplicate a record to any destination group, creating an independent copy

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

duplicate_record Rate-limited

duplicate_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": {
    "duplicate_record": {
      "limits": [
        {
          "counter": "duplicate_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 duplicate_record

What does the duplicate_record tool do? +

Duplicate a record to any destination group, creating an independent copy. 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 duplicate_record? +

Register the Devon MCP server in PolicyLayer and add a rule for duplicate_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 duplicate_record? +

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

Can I rate-limit duplicate_record? +

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

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

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