Create a new empty estimate. Returns an estimate ID to use with add_service and export_estimate.
AI agents use create_estimate to create or update resources in Aws Calculator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aws Calculator environment.
This tool creates a new AWS cost estimate object, which is a write operation that generates data. It has no side effects beyond creating a data record that can be modified or deleted later. The blast radius is minimal — creating an estimate is harmless and fully reversible. No destruction, execution of external code, or financial commitment occurs.
From the tool's definition Tool description states 'Create a new empty estimate' — a create operation that produces a new resource (estimate ID) with reversible effects.
Documented attack patterns abuse exactly the kind of access create_estimate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aws Calculator, and nothing reaches the server without passing your rules. This is the rule we recommend for create_estimate:
{
"version": "1",
"default": "deny",
"tools": {
"create_estimate": {
"limits": [
{
"counter": "create_estimate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_estimate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new empty estimate. Returns an estimate ID to use with add_service and export_estimate. It is categorised as a Write tool in the Aws Calculator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aws Calculator MCP server in PolicyLayer and add a rule for create_estimate: 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 Aws Calculator. Nothing to install.
create_estimate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_estimate 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 create_estimate. 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.
create_estimate is provided by the Aws Calculator MCP server (musheer360/aws-calculator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Aws Calculator, 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.
8 Aws Calculator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.