configure_android
Configure Android-specific project settings including package name, keystore, and permissions
This record as markdown: /tools/keeveeg-godot-mcp/configure-android.md
What configure_android does on Godot
AI agents use configure_android to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
settings | object | Yes | Android settings to configure |
Parameters from the server's own tool schema.
Why configure_android is rated Medium
This tool creates or modifies reversible project configuration data (Android settings, keystore details, permissions). It does not execute commands, delete data, or move money, placing it in Write. Severity is high because misconfiguration or malicious modification of keystore and permissions could compromise app security, enable unauthorized access, or cause deployment failures.
From the tool's definition Tool configures project settings including package name, keystore, and permissions—modifying Android build and security configurations that affect app deployment and behavior.
Attacks that exploit this kind of access
The rule that runs configure_android safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For configure_android, this is the rule to start with:
configure_android stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every configure_android call is checked against it from then on.
Questions about configure_android
Configure Android-specific project settings including package name, keystore, and permissions. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
configure_android accepts 1 parameter: settings. Required: settings. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for configure_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. Nothing to install.
configure_android is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the configure_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.
Set action: deny in the PolicyLayer policy for configure_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.
configure_android is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue