AI agents invoke focus_viewport to trigger actions in PlayCanvas Editor MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Focusing the viewport triggers an external operation in the PlayCanvas Editor (changing the editor's camera/view state). It does not read or write persistent data, but it does cause a side effect in the running application's UI state. It is not destructive, financial, or a pure read — it executes a UI/viewport action in the editor environment.
From the tool's definition Focus viewport on entities
Documented attack patterns abuse exactly the kind of access focus_viewport 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 focus_viewport:
{
"version": "1",
"default": "deny",
"tools": {
"focus_viewport": {
"limits": [
{
"counter": "focus_viewport_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}focus_viewport stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Focus viewport on entities. It is categorised as a Execute tool in the PlayCanvas Editor MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PlayCanvas Editor MCP Server MCP server in PolicyLayer and add a rule for focus_viewport: 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.
focus_viewport is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the focus_viewport 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 focus_viewport. 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.
focus_viewport 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.