get_billing_usage
AI agents call get_billing_usage to retrieve information from Sablier MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves billing and usage metrics, which are informational data with no side effects. While the description is empty, the 'get_' prefix and context within a financial analysis platform strongly suggest a simple data retrieval operation. The low severity reflects that misuse would expose usage/billing information rather than enable modification of systems or financial transactions.
From the tool's definition Tool name 'get_billing_usage' indicates retrieval of billing/usage data. No description provided, but the naming convention 'get_*' is consistent with read-only query operations observed in sibling tools (get_billing_usage, check_flow_job,…
Attacks that exploit this kind of access
get_billing_usage. It is categorised as a Read tool in the Sablier MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for get_billing_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 Sablier MCP Server. Nothing to install.
get_billing_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_billing_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_billing_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_billing_usage is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →