get_subscription
Return the caller's OWN Stripe subscription(s) — status/price/product/quantity/period/trial/cancel-at-period-end (from stripe_subscriptions, owner-scoped to the caller's OAuth sub). A billing:view operator (admin via grants_all) may pass all_users:true for the whole fleet. Returns { count, subscr...
This record as markdown: /tools/dev-busymate-busymate-devtools/get-subscription.md
What get_subscription does on Busymate DevTools
AI agents call get_subscription 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 |
|---|---|---|---|
all_users | boolean | — | billing:view/admin only — return EVERY account's subscriptions instead of just the caller's. |
Parameters from the server's own tool schema.
Why get_subscription is rated Low
Although this tool accesses financial subscription data (Stripe), it performs only read operations—retrieving subscription status and pricing information. The blast radius is limited because: (1) it returns only the caller's own data by default (owner-scoped), (2) an admin with `all_users:true` could view the fleet's subscriptions, creating moderate information disclosure risk, and (3) no financial transactions,…
From the tool's definition 'Return the caller's OWN Stripe subscription(s)' and 'owner-scoped to the caller's OAuth sub' indicate data retrieval.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_subscription 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_subscription, this is the rule to start with:
get_subscription 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_subscription call is checked against it from then on.
Questions about get_subscription
Return the caller's OWN Stripe subscription(s) — status/price/product/quantity/period/trial/cancel-at-period-end (from stripe_subscriptions, owner-scoped to the caller's OAuth sub). A billing:view operator (admin via grants_all) may pass all_users:true for the whole fleet. Returns { count, subscriptions:[…] }. Phase 1 is Stripe TEST mode. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_subscription accepts 1 parameter: all_users. 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_subscription: 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_subscription 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_subscription 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_subscription. 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_subscription 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