List assets. Returns summary by default (id, name, type, folder, tags). Use full=true for complete asset data.
AI agents call list_assets to retrieve information from PlayCanvas Editor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries asset metadata without side effects. It is a straightforward read operation that returns data about assets in the PlayCanvas project. The optional 'full' parameter only controls the depth of returned information, not any mutative action.
From the tool's definition Tool name is 'list_assets' and description states it 'List assets' with optional return of summary or complete asset data. No modification, deletion, or execution occurs.
Documented attack patterns abuse exactly the kind of access list_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 list_assets:
{
"version": "1",
"default": "deny",
"tools": {
"list_assets": {}
}
} list_assets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List assets. Returns summary by default (id, name, type, folder, tags). Use full=true for complete asset data. It is categorised as a Read tool in the PlayCanvas Editor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PlayCanvas Editor MCP Server MCP server in PolicyLayer and add a rule for list_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.
list_assets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_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.