Clear all queued in-world user messages (useful after processing a batch).
AI agents call clearPendingMessages to permanently remove resources in Maige 3d — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly clears/purges all pending messages from a queue. Once cleared, those queued messages are gone and cannot be recovered, making it a destructive operation. The blast radius is medium — it only affects the message queue within the 3D scene context, not broader data or financial systems.
From the tool's definition Clear all queued in-world user messages
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all queued in-world user messages (useful after processing a batch). It is categorised as a Destructive tool in the Maige 3d MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Maige 3d MCP server in PolicyLayer and add a rule for clearPendingMessages: 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.
clearPendingMessages is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clearPendingMessages 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 clearPendingMessages. 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.
clearPendingMessages 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 →