Open an estimate URL in a headless browser, trigger cost recalculation, and return the updated pricing. This is the ONLY way to get actual dollar amounts — the API does not calculate costs. Automatically retries once after 15s if costs show $0 (propagation delay). Requires Chrome/Chromium.
AI agents invoke refresh_estimate to trigger actions in Aws Calculator. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool automates browser actions (opening URLs, triggering recalculation, waiting for propagation) through headless Chrome. While it doesn't delete data or move money, it performs external operations (browser automation) whose effects depend on which estimate URL is passed as an argument.
From the tool's definition The tool description explicitly states 'Open an estimate URL in a headless browser, trigger cost recalculation' and 'Requires Chrome/Chromium.' These phrases indicate the tool executes code in a browser environment to trigger calculations, which is an Execute…
Documented attack patterns abuse exactly the kind of access refresh_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 refresh_estimate:
{
"version": "1",
"default": "deny",
"tools": {
"refresh_estimate": {
"limits": [
{
"counter": "refresh_estimate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}refresh_estimate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open an estimate URL in a headless browser, trigger cost recalculation, and return the updated pricing. This is the ONLY way to get actual dollar amounts — the API does not calculate costs. Automatically retries once after 15s if costs show $0 (propagation delay). Requires Chrome/Chromium. It is categorised as a Execute tool in the Aws Calculator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aws Calculator MCP server in PolicyLayer and add a rule for refresh_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.
refresh_estimate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the refresh_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 refresh_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.
refresh_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.