get_credits
AI agents call get_credits 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.
The tool appears to retrieve account credit data without side effects. While the empty description reduces confidence, the naming convention ('get_*') and sibling tool context (financial transactions like 'buy_credit_pack' are separate) suggest this is a query operation. No evidence of data modification, deletion, code execution, or financial transaction initiation.
From the tool's definition Tool name 'get_credits' suggests querying or retrieving credit balance information. The description is empty, limiting clarity, but the name pattern and context (credit pack purchases available via 'buy_credit_pack') indicate a read operation to check credit…
Attacks that exploit this kind of access
get_credits. 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_credits: 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_credits 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_credits 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_credits. 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_credits 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 →