Show usage quotas and limits: storage, sessions, retention age.
AI agents call check_quotas to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays current usage quotas and system limits (storage, sessions, retention age). It is purely informational—retrieving data about system state without creating, modifying, deleting, or executing anything. This is a read-only operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'check_quotas' and description 'Show usage quotas and limits' indicates retrieval of quota/limit information with no modification or execution of operations.
Documented attack patterns abuse exactly the kind of access check_quotas gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for check_quotas:
{
"version": "1",
"default": "deny",
"tools": {
"check_quotas": {}
}
} check_quotas 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.
Show usage quotas and limits: storage, sessions, retention age. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for check_quotas: 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 Claude Code Toolkit. Nothing to install.
check_quotas 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_quotas 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_quotas. 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_quotas is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, 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.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.