AI agents call getPendingUserMessages 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 chat messages that users have typed within a 3D environment. It performs no side effects, does not modify or delete data, does not execute commands, and does not involve financial operations. It is a straightforward read operation that simply accesses and returns existing data.
From the tool's definition Tool description states 'Return any in-world chat messages' — a retrieval operation with no modification, deletion, or execution of code. The verb 'Return' and context of reading user input messages from a chat system indicates a read-only query.
Attacks that exploit this kind of access
Return any in-world chat messages the user has typed from inside the 3D environment. 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 getPendingUserMessages: 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.
getPendingUserMessages 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 getPendingUserMessages 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 getPendingUserMessages. 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.
getPendingUserMessages 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 →