AI agents use duplicate_entities to create or update resources in PlayCanvas Editor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PlayCanvas Editor MCP Server environment.
Duplicating entities creates new scene objects in the PlayCanvas editor, which is a Write operation (reversible creation/modification of data). Severity is medium because while duplicates can be deleted and the action is undone, uncontrolled duplication could bloat a scene with unwanted entities.
From the tool's definition The tool name 'duplicate_entities' and description 'Duplicate entities' indicate creation of new entity copies in the PlayCanvas scene.
Documented attack patterns abuse exactly the kind of access duplicate_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PlayCanvas Editor MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for duplicate_entities:
{
"version": "1",
"default": "deny",
"tools": {
"duplicate_entities": {
"limits": [
{
"counter": "duplicate_entities_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}duplicate_entities 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.
Free to start. No card required.
Duplicate entities. It is categorised as a Write tool in the PlayCanvas Editor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PlayCanvas Editor MCP Server MCP server in PolicyLayer and add a rule for duplicate_entities: 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 PlayCanvas Editor MCP Server. Nothing to install.
duplicate_entities 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_entities 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_entities. 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_entities is provided by the PlayCanvas Editor MCP Server MCP server (playcanvas/editor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 PlayCanvas Editor MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
23 PlayCanvas Editor MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.