AI agents call getSceneState to retrieve information from Maige 3d 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 the current state of a 3D scene. It performs a read-only operation that returns information about objects, lights, camera settings, and environment without creating, modifying, deleting, or executing any operations. The recommendation to 'call this first before making any changes' confirms it is purely informational. No side effects or data mutations occur.
From the tool's definition Tool name 'getSceneState' and description 'Get the full current scene state: all objects, lights, camera, and environment' indicates retrieval of scene data with no modifications or side effects.
Attacks that exploit this kind of access
Get the full current scene state: all objects, lights, camera, and environment. Call this first before making any changes. It is categorised as a Read tool in the Maige 3d MCP Server, which means it retrieves data without modifying state.
Register the Maige 3d MCP server in PolicyLayer and add a rule for getSceneState: 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 Maige 3d. Nothing to install.
getSceneState 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 getSceneState 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 getSceneState. 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.
getSceneState is provided by the Maige 3d MCP server (m-ai-gexr/mcp-webgpu). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →