list_push_tokens
List registered device push tokens (masked), PLATFORM-ROUTED (#1542): each device_push_tokens row carries a platform discriminator — ios = an APNs device token (push-notify's APNs leg), android = an FCM registration token (push-notify's FCM HTTP v1 leg). The column defaults ios, so legacy rows re...
This record as markdown: /tools/dev-busymate-busymate-devtools/list-push-tokens.md
What list_push_tokens does on Busymate DevTools
AI agents call list_push_tokens to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
deviceName | string | — | |
device_uuid | string | — |
Parameters from the server's own tool schema.
Why list_push_tokens is rated Low
Even though list_push_tokens only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_push_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_push_tokens, this is the rule to start with:
list_push_tokens 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 Busymate DevTools, apply this rule, and every list_push_tokens call is checked against it from then on.
Questions about list_push_tokens
List registered device push tokens (masked), PLATFORM-ROUTED (#1542): each device_push_tokens row carries a platform discriminator — ios = an APNs device token (push-notify's APNs leg), android = an FCM registration token (push-notify's FCM HTTP v1 leg). The column defaults ios, so legacy rows read ios. Optionally scope to one device. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
list_push_tokens accepts 2 parameters: deviceName, device_uuid. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for list_push_tokens: 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 Busymate DevTools. Nothing to install.
list_push_tokens 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_push_tokens 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_push_tokens. 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_push_tokens is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue