AI agents use create_assets 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.
The tool performs a create operation on assets, which falls under Write category (creates or modifies data reversibly). Severity is medium because: (1) asset creation is generally reversible (assets can be deleted via the sibling delete_assets tool), (2) the blast radius is moderate—erroneous asset creation could clutter the project but won't destroy existing work, and (3) it doesn't execute arbitrary code, delete…
From the tool's definition Tool name 'create_assets' and description 'Create assets' indicate the tool creates/adds new assets to the PlayCanvas project. This is a reversible write operation that modifies project state by introducing new asset objects.
Documented attack patterns abuse exactly the kind of access create_assets 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 create_assets:
{
"version": "1",
"default": "deny",
"tools": {
"create_assets": {
"limits": [
{
"counter": "create_assets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_assets 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.
Create assets. 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 create_assets: 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.
create_assets 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 create_assets 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 create_assets. 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.
create_assets 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.