Add one or more AWS services to an estimate. Field values follow these patterns based on field type: - numericInput: plain string value, e.g.
AI agents use add_service 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.
Adding services to an estimate modifies the calculator state in a meaningful way that affects cost calculations and the resulting shareable links. While this does not execute arbitrary code or delete data, it does alter the estimate document structure, making it a Write operation.
From the tool's definition Tool "add_service" creates or modifies data by adding AWS services to an estimate. The description states it adds services and accepts field values, which are persisted to the estimate object. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access add_service 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 add_service:
{
"version": "1",
"default": "deny",
"tools": {
"add_service": {
"limits": [
{
"counter": "add_service_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_service 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.
Add one or more AWS services to an estimate. Field values follow these patterns based on field type: - numericInput: plain string value, e.g. 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 add_service: 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.
add_service 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 add_service 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 add_service. 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.
add_service 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.