AI agents call describe_severity_levels 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.
The tool appears to retrieve or list severity level definitions without modifying or executing any operations. 'Describe' is a standard read operation pattern. Confidence is moderate (0.7) because the description is empty and provides no additional detail about what severity levels it returns or whether it has side effects. The tool name alone suggests informational retrieval with no blast radius.
From the tool's definition Tool name 'describe_severity_levels' indicates a retrieval operation that queries or lists severity level definitions. No parameters or description provided, but the verb 'describe' typically performs read-only operations.
Documented attack patterns abuse exactly the kind of access describe_severity_levels 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 describe_severity_levels:
{
"version": "1",
"default": "deny",
"tools": {
"describe_severity_levels": {}
}
}describe_severity_levels 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.
describe_severity_levels. 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 describe_severity_levels: 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.
describe_severity_levels 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 describe_severity_levels 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 describe_severity_levels. 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.
describe_severity_levels 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.