AI agents call get-cost-and-usage to retrieve information from Prometheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial and operational metrics from AWS Managed Prometheus without altering data. Even though it touches financial data, it only reads/reports costs rather than moving money or committing financial obligations, placing it in Read rather than Financial. The empty description introduces minor uncertainty, but the naming convention strongly suggests a passive data retrieval operation.
From the tool's definition Tool name 'get-cost-and-usage' indicates retrieval of cost and usage metrics without modification. The empty description prevents full certainty, but the verb 'get' and the query-like nature (cost/usage data retrieval) are consistent with a Read operation.
Documented attack patterns abuse exactly the kind of access get-cost-and-usage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-cost-and-usage:
{
"version": "1",
"default": "deny",
"tools": {
"get-cost-and-usage": {}
}
}get-cost-and-usage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get-cost-and-usage. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for get-cost-and-usage: 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 Prometheus MCP Server. Nothing to install.
get-cost-and-usage 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 get-cost-and-usage 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 get-cost-and-usage. 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.
get-cost-and-usage is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, 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.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.