Estimate the cost of an API call to a specific model. Use this BEFORE making expensive API calls to understand the cost impact.
AI agents call estimate_cost to retrieve information from AgentCost MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only cost estimation calculation. It queries pricing data and returns information to inform decision-making, but does not execute payments, modify budgets, or trigger external operations. The tool has no side effects and provides informational output only.
From the tool's definition Tool name 'estimate_cost' and description 'Estimate the cost of an API call to a specific model' indicate a query/calculation operation.
Attacks that exploit this kind of access
Estimate the cost of an API call to a specific model. Use this BEFORE making expensive API calls to understand the cost impact. It is categorised as a Read tool in the AgentCost MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AgentCost MCP Server 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 AgentCost MCP Server. Nothing to install.
estimate_cost 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 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.
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.
estimate_cost is provided by the AgentCost MCP Server MCP server (oneagentlabs/agentcost-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 →