cost-anomaly
AI agents call cost-anomaly to retrieve information from Amazon MQ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern implies retrieval and analysis of cost/anomaly data rather than modification or execution. Without a description, confidence is moderate. If this tool merely queries cost metrics or generates reports on anomalies, it is Read. However, the empty description prevents complete certainty of actual behavior.
From the tool's definition Tool name 'cost-anomaly' suggests analysis or querying of cost data for anomalies, with no explicit destructive, write, or execute operations indicated. Description is empty, which reduces confidence.
Attacks that exploit this kind of access
cost-anomaly. It is categorised as a Read tool in the Amazon MQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for cost-anomaly: 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 Amazon MQ MCP Server. Nothing to install.
cost-anomaly 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-anomaly 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-anomaly. 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-anomaly is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.