deploy_to_android · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_to_android does on Godot MCP Server

AI agents invoke deploy_to_android to trigger actions in Godot 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.

WHY IT NEEDS A POLICY

Why deploy_to_android needs a policy

Building and deploying to an Android device constitutes execution of the compilation toolchain and transfer of compiled artifacts to external hardware. This is Execute-category (not Destructive, as it does not irreversibly delete data; not Write, as it goes beyond data modification into running complex external processes).

From the tool's definition Tool performs 'Build and deploy' operations, which are code execution and external device operations. Described as triggering a build pipeline and device deployment—actions whose effects depend on project configuration and target device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_to_android Rate-limited

deploy_to_android 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": {
    "deploy_to_android": {
      "limits": [
        {
          "counter": "deploy_to_android_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 Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about deploy_to_android

What does the deploy_to_android tool do? +

Build and deploy the project to a connected Android device. It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_to_android? +

Register the Godot MCP Server MCP server in PolicyLayer and add a rule for deploy_to_android: 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 Godot MCP Server. Nothing to install.

What risk level is deploy_to_android? +

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

Can I rate-limit deploy_to_android? +

Yes. Add a rate_limit block to the deploy_to_android 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 deploy_to_android completely? +

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

deploy_to_android is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.