AI agents call list-cost-allocation-tags 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 cost allocation tags from AWS, which is a read-only query operation. The empty description prevents confirmation of side effects, but the naming convention strongly indicates data retrieval with no mutations. Cost tag metadata is informational and non-sensitive enough to classify as low severity even if unexpectedly exposed to an AI agent, as listing tags cannot move money or delete resources.
From the tool's definition Tool name 'list-cost-allocation-tags' indicates a listing/retrieval operation. The verb 'list' is a read-only operation that queries and returns cost allocation tag metadata without modification.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list-cost-allocation-tags 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 list-cost-allocation-tags:
{
"version": "1",
"default": "deny",
"tools": {
"list-cost-allocation-tags": {}
}
}list-cost-allocation-tags 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.
list-cost-allocation-tags. 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 list-cost-allocation-tags: 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.
list-cost-allocation-tags 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 list-cost-allocation-tags 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 list-cost-allocation-tags. 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.
list-cost-allocation-tags 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.