Check workspace balance, tier, and remaining calls in this billing period.
AI agents call check_balance to retrieve information from APIClaw 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 information from the workspace without modifying any data, executing code, or causing irreversible changes. It is a straightforward read operation similar to get_usage_summary and check_workspace_status (sibling tools). The blast radius of misuse is minimal—an attacker could only see billing details, not manipulate them.
From the tool's definition Tool description states 'Check workspace balance, tier, and remaining calls' - a pure query operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access check_balance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for check_balance:
{
"version": "1",
"default": "deny",
"tools": {
"check_balance": {}
}
}check_balance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check workspace balance, tier, and remaining calls in this billing period. It is categorised as a Read tool in the APIClaw MCP Server, which means it retrieves data without modifying state.
Register the APIClaw MCP server in PolicyLayer and add a rule for check_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 APIClaw. Nothing to install.
check_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 check_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 check_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.
check_balance is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from APIClaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 APIClaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.