get_usage
Return the caller's OWN metered usage rollup (metric captured_entries = count of captured entries per device per period; from stripe_usage_events, owner-scoped to the caller's OAuth sub) aggregated by period over a window. since_days (default 30, max 365), metric (default captured_entries). A bil...
This record as markdown: /tools/dev-busymate-busymate-devtools/get-usage.md
What get_usage does on Busymate DevTools
AI agents call get_usage 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 |
|---|---|---|---|
metric | string | — | Usage metric (default 'captured_entries'). |
user_id | string | — | billing:view/admin only — a specific target user. |
all_users | boolean | — | billing:view/admin only — return EVERY account's usage. |
since_days | number | — | Look back this many days (1–365, default 30). |
Parameters from the server's own tool schema.
Why get_usage is rated Low
This tool queries and returns usage statistics and billing metrics. It performs no modifications, deletions, or financial transactions—it only retrieves metered usage data. Even though a `billing:view` operator may query fleet-wide usage with `all_users:true`, the operation remains a read/query action.
From the tool's definition Returns the caller's OWN metered usage rollup aggregated by period; retrieves usage data without modification. Description explicitly states 'Return' and 'owner-scoped to the caller's OAuth sub', indicating read-only data retrieval of billing metrics.
Attacks that exploit this kind of access
The rule that runs get_usage 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 get_usage, this is the rule to start with:
get_usage 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 get_usage call is checked against it from then on.
Questions about get_usage
Return the caller's OWN metered usage rollup (metric captured_entries = count of captured entries per device per period; from stripe_usage_events, owner-scoped to the caller's OAuth sub) aggregated by period over a window. since_days (default 30, max 365), metric (default captured_entries). A billing:view operator may pass all_users:true for the fleet. Returns { metric, since, count, total_quantity, usage:[{period_start, device_uuid, quantity, reported_at}] }. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_usage accepts 4 parameters: metric, user_id, all_users, since_days. 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 get_usage: 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.
get_usage 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 get_usage 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 get_usage. 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.
get_usage 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