sensor_notifications
Read the notification shade from Android. Returns a parsed list of active notifications with title, text, package, and time. iOS: not supported.
This record as markdown: /tools/alexgladkov-claude-in-mobile/sensor-notifications.md
What sensor_notifications does on Claude Mobile
AI agents call sensor_notifications to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sensor_notifications is rated Low
This tool retrieves and queries notification data from an Android device without creating, modifying, deleting, or executing any operations. It has no side effects and does not alter device state. While notifications may contain sensitive information, the tool itself is purely informational. Confidence is high because the description is explicit and unambiguous about its read-only nature.
From the tool's definition Tool description states it 'Read the notification shade from Android' and 'Returns a parsed list of active notifications with title, text, package, and time.' The verb 'Read' and the explicit retrieval of notification data without modification indicate a…
Attacks that exploit this kind of access
The rule that runs sensor_notifications 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 sensor_notifications, this is the rule to start with:
sensor_notifications is read-only, so it stays allowed. 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 sensor_notifications call is checked against it from then on.
Questions about sensor_notifications
Read the notification shade from Android. Returns a parsed list of active notifications with title, text, package, and time. iOS: not supported. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for sensor_notifications: 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.
sensor_notifications 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 sensor_notifications 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 sensor_notifications. 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.
sensor_notifications 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.
This server
Across the catalogue