Send a configured app debug broadcast intent from config/apps.json.
AI agents invoke android_send_debug_intent to trigger actions in DevLab MCP Suite. 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.
This tool sends a broadcast intent to an Android app, which triggers external operations on the device. Broadcast intents can cause apps to perform actions, change state, or execute code paths. This falls under Execute since it triggers operations whose effects depend on which intent is sent and what the receiving app does with it.
From the tool's definition Send a configured app debug broadcast intent from config/apps.json
Attacks that exploit this kind of access
Send a configured app debug broadcast intent from config/apps.json. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_send_debug_intent: 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 DevLab MCP Suite. Nothing to install.
android_send_debug_intent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the android_send_debug_intent 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 android_send_debug_intent. 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.
android_send_debug_intent is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). 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 →