List Android devices connected via ADB.
AI agents call list_android_devices to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about connected Android devices without modifying state, executing code, or triggering side effects. It is a read-only operation that gathers existing data from ADB. The low severity reflects minimal blast radius—even if an AI agent misuses this tool, it can only enumerate devices, not interact with them or cause harm.
From the tool's definition Tool name 'list_android_devices' and description 'List Android devices connected via ADB' indicate a query/retrieval operation with no modification or execution of commands.
Attacks that exploit this kind of access
List Android devices connected via ADB. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for list_android_devices: 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.
list_android_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_android_devices 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 list_android_devices. 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.
list_android_devices 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.
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 →