adb_notifications
Read active notifications on the device. Parses the notification manager dump to extract package, title, text, importance, channel, and flags for each notification. Useful for verifying push notification delivery, monitoring notification state, and testing notification-related features.
This record as markdown: /tools/io-github-fullread-deepadb/adb-notifications.md
What adb_notifications does on Deepadb
AI agents call adb_notifications to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_notifications is rated Low
This tool retrieves and queries notification state from the device without creating, modifying, deleting, or executing any operations. It is purely observational—parsing existing notification manager data to extract metadata (package, title, text, importance, channel, flags). The stated use cases (verifying delivery, monitoring state, testing) all involve inspection only.
From the tool's definition Tool description explicitly states 'Read active notifications on the device' and describes it as parsing/extracting notification data with no modification or deletion capability mentioned.
Attacks that exploit this kind of access
The rule that runs adb_notifications safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_notifications, this is the rule to start with:
adb_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 Deepadb, apply this rule, and every adb_notifications call is checked against it from then on.
Questions about adb_notifications
Read active notifications on the device. Parses the notification manager dump to extract package, title, text, importance, channel, and flags for each notification. Useful for verifying push notification delivery, monitoring notification state, and testing notification-related features. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_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 Deepadb. Nothing to install.
adb_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 adb_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 adb_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.
adb_notifications is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue