Export an estimate to calculator.aws and get a shareable URL. The link will show the full estimate with AWS-calculated pricing.
AI agents use export_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 new data artifacts (shareable calculator.aws URLs) and exports estimate information to an external platform. While not destructive or irreversible, it involves creating/writing data to a remote service.
From the tool's definition Tool 'export_estimate' creates and generates a shareable URL on calculator.aws, which represents persisting the estimate data to an external service.
Documented attack patterns abuse exactly the kind of access export_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 export_estimate:
{
"version": "1",
"default": "deny",
"tools": {
"export_estimate": {
"limits": [
{
"counter": "export_estimate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_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.
Export an estimate to calculator.aws and get a shareable URL. The link will show the full estimate with AWS-calculated pricing. 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 export_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.
export_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 export_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 export_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.
export_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.