AI agents call store_search 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 performs a search operation, which is fundamentally a read-only action. It retrieves or queries assets from a store without creating, modifying, or deleting any data. The blast radius of misuse is minimal—an agent could at worst perform exhaustive searches or return unwanted search results, but cannot damage data or cause external operations. Classified as Read with low severity.
From the tool's definition Tool name 'store_search' and description 'Search store assets' indicate a query operation that retrieves data from a store without modification or side effects.
Documented attack patterns abuse exactly the kind of access store_search 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 store_search:
{
"version": "1",
"default": "deny",
"tools": {
"store_search": {}
}
}store_search 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.
Search store assets. 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 store_search: 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.
store_search 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 store_search 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 store_search. 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.
store_search 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.