Remove components from entity
AI agents call remove_components to permanently remove resources in PlayCanvas Editor MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing components from an entity is an irreversible destructive action — it destroys the component and its configuration data. Unlike toggling or disabling a component, removal cannot typically be undone without manual recreation, making this a Destructive operation with high blast radius if misused by an AI agent on critical entities.
From the tool's definition Remove components from entity
Documented attack patterns abuse exactly the kind of access remove_components 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 remove_components:
{
"version": "1",
"default": "deny",
"hide": [
"remove_components"
]
}remove_components disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove components from entity. It is categorised as a Destructive tool in the PlayCanvas Editor MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PlayCanvas Editor MCP Server MCP server in PolicyLayer and add a rule for remove_components: 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.
remove_components is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_components 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 remove_components. 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.
remove_components 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.