intent_broadcast
Send an Android broadcast intent. Useful for triggering system events or communicating with broadcast receivers. Android only.
This record as markdown: /tools/alexgladkov-claude-in-mobile/intent-broadcast.md
What intent_broadcast does on Claude Mobile
AI agents invoke intent_broadcast to trigger actions in Claude Mobile. 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 intent_broadcast is rated High
Broadcasting intents on Android can trigger arbitrary system events and app receivers, including launching activities, triggering services, sending SMS, manipulating system state, or activating malicious receivers. This is an execution primitive with a wide blast radius depending on the intent action and data sent. It is reversible in some cases but the primary effect is executing operations on the device.
From the tool's definition 'Send an Android broadcast intent' and 'triggering system events or communicating with broadcast receivers'
Attacks that exploit this kind of access
The rule that runs intent_broadcast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For intent_broadcast, this is the rule to start with:
intent_broadcast 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every intent_broadcast call is checked against it from then on.
Questions about intent_broadcast
Send an Android broadcast intent. Useful for triggering system events or communicating with broadcast receivers. Android only. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for intent_broadcast: 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 Claude Mobile. Nothing to install.
intent_broadcast 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 intent_broadcast 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 intent_broadcast. 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.
intent_broadcast is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue