AI agents use duplicate_page to create or update resources in Pen — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pen environment.
This tool creates and modifies document content by duplicating a page and inserting it, which constitutes a Write operation. It does not execute arbitrary code, destroy data irreversibly, or move funds. Severity is medium because misuse could clutter documents or create unwanted duplicates, but the effect is easily undone by deleting the duplicate page.
From the tool's definition Tool description states 'Duplicate a page (deep-clone with new IDs) and insert the copy right after the original' — this creates new data (cloned page) and modifies document structure by inserting it. The operation is reversible (the duplicate can be deleted).
Attacks that exploit this kind of access
Duplicate a page (deep-clone with new IDs) and insert the copy right after the original. It is categorised as a Write tool in the Pen MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pen MCP server in PolicyLayer and add a rule for duplicate_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 Pen. Nothing to install.
duplicate_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the duplicate_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.
Set action: deny in the PolicyLayer policy for duplicate_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.
duplicate_page is provided by the Pen MCP server (@zseven-w/pen-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →