Low Risk

estimate_cost

Estimate API costs based on token usage across all conversations.

How to control estimate_cost ↓

What estimate_cost does on Claude Code Toolkit

AI agents call estimate_cost 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.

Low Risk

Why estimate_cost needs a policy

This tool retrieves and analyzes token usage metrics to produce a cost estimate. It performs no side effects, creates no resources, executes no code or commands, and causes no data loss. It is purely informational, fitting the Read category definition of 'retrieves or queries data; no side effects'.

From the tool's definition Tool name 'estimate_cost' and description 'Estimate API costs based on token usage across all conversations' indicate a calculation/estimation operation that queries existing data without modifying, deleting, or executing external operations.

Documented attack patterns abuse exactly the kind of access estimate_cost gives an agent:

How to control estimate_cost

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 estimate_cost:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "estimate_cost": {}
  }
}

estimate_cost is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Code Toolkit — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about estimate_cost

What does the estimate_cost tool do? +

Estimate API costs based on token usage across all conversations. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on estimate_cost? +

Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for estimate_cost: 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.

What risk level is estimate_cost? +

estimate_cost is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit estimate_cost? +

Yes. Add a rate_limit block to the estimate_cost 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.

How do I block estimate_cost completely? +

Set action: deny in the PolicyLayer policy for estimate_cost. 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.

What MCP server provides estimate_cost? +

estimate_cost 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.

Enforce policy on every Claude Code Toolkit tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.