cost_explorer_by_service
AI agents call cost_explorer_by_service to retrieve information from AWS MCP Audit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes AWS cost data by service. The server is explicitly described as 'read-only' and designed for assessment and reporting. Cost exploration returns financial insights but does not move money, modify infrastructure, or execute operations. No side effects or destructive capability.
From the tool's definition Tool name 'cost_explorer_by_service' and server description states 'read-only assessment' with 'cost analysis'. Sibling tools include 'cost_explorer_summary_tool' and 'cost_signals', all consistent with querying cost data without modification.
Attacks that exploit this kind of access
cost_explorer_by_service. It is categorised as a Read tool in the AWS MCP Audit MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP Audit MCP server in PolicyLayer and add a rule for cost_explorer_by_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 MCP Audit. Nothing to install.
cost_explorer_by_service 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 cost_explorer_by_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 cost_explorer_by_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.
cost_explorer_by_service is provided by the AWS MCP Audit MCP server (oldcoder01/aws-mcp-audit). 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 →