executeScript · Maige 3d MCP: Risk & Policy

WHAT IT DOES

What executeScript does on Maige 3d

AI agents invoke executeScript to trigger actions in Maige 3d. 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.

WHY IT NEEDS A POLICY

Why executeScript needs a policy

This tool allows execution of arbitrary JavaScript in a browser context, which is an Execute-category capability with critical severity. An AI agent misusing this could run malicious scripts, modify DOM elements, access sensitive data, exfiltrate information, perform actions on behalf of the user, or compromise the integrity of the 3D scene and any connected systems.

From the tool's definition Tool name and description: 'Execute arbitrary JavaScript code in the connected browser scene context.' The word 'arbitrary' and 'execute' directly indicate the tool runs code with unrestricted scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

executeScript Rate-limited

executeScript 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "executeScript": {
      "limits": [
        {
          "counter": "executescript_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Maige 3d, so you can run agents against it safely.

FAQ

Questions about executeScript

What does the executeScript tool do? +

Execute arbitrary JavaScript code in the connected browser scene context. It is categorised as a Execute tool in the Maige 3d MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on executeScript? +

Register the Maige 3d MCP server in PolicyLayer and add a rule for executeScript: 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.

What risk level is executeScript? +

executeScript is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit executeScript? +

Yes. Add a rate_limit block to the executeScript 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.

How do I block executeScript completely? +

Set action: deny in the PolicyLayer policy for executeScript. 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.

What MCP server provides executeScript? +

executeScript 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.