GET /v1/credits/balance. Returns credits_balance and balances (one_off, recurring, rollover, total).
AI agents call get_credits_balance to retrieve information from DataMerge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a GET request to fetch credit balance metrics. It has no side effects, does not create, modify, or delete data, and does not execute external operations. While it reveals financial account information, the tool itself only reads data and does not commit financial obligations or move money.
From the tool's definition Tool name 'get_credits_balance' and description 'GET /v1/credits/balance. Returns credits_balance and balances' indicate a read-only query operation that retrieves account balance information without modifying any data.
Attacks that exploit this kind of access
GET /v1/credits/balance. Returns credits_balance and balances (one_off, recurring, rollover, total). It is categorised as a Read tool in the DataMerge MCP MCP Server, which means it retrieves data without modifying state.
Register the DataMerge MCP server in PolicyLayer and add a rule for get_credits_balance: 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 DataMerge MCP. Nothing to install.
get_credits_balance 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_balance 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_balance. 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_balance is provided by the DataMerge MCP server (poolside-ventures/datamerge-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 →