install_android_build_template · Godot MCP: Risk & Policy

WHAT IT DOES

What install_android_build_template does on Godot MCP

AI agents invoke install_android_build_template to trigger actions in Godot MCP. 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 install_android_build_template needs a policy

This tool executes an external process (godot CLI), extracts archive files into the project directory, and modifies configuration files. It triggers multiple filesystem-modifying operations and external command execution. While it writes files, the primary action is executing a multi-step external process with side effects that depend on the environment, making Execute the most appropriate category.

From the tool's definition Runs godot --install-android-build-template, extracts android_source.zip into android/build/, pins config.gradle

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_android_build_template Rate-limited

install_android_build_template 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": {
    "install_android_build_template": {
      "limits": [
        {
          "counter": "install_android_build_template_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, so you can run agents against it safely.

FAQ

Questions about install_android_build_template

What does the install_android_build_template tool do? +

Bundle the 5-step Android build template install recipe into one call. Runs godot --install-android-build-template, extracts android_source.zip into android/build/, pins config.gradle. It is categorised as a Execute tool in the Godot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_android_build_template? +

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

What risk level is install_android_build_template? +

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

Can I rate-limit install_android_build_template? +

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

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

install_android_build_template is provided by the Godot MCP server (jamesdowzard/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.