Get current SLO status — availability and latency burn rates.
AI agents call get_slo_status to retrieve information from Kubernetes + Prometheus SRE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns observability data (SLO metrics, burn rates) from a monitoring system without creating, modifying, or deleting any resources. It is a passive read operation with no blast radius beyond information disclosure. It aligns with tools like 'get_pod_logs' and 'get_node_health' on the same server, all of which are informational queries.
From the tool's definition Tool name 'get_slo_status' and description 'Get current SLO status — availability and latency burn rates' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Get current SLO status — availability and latency burn rates. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for get_slo_status: 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 Kubernetes + Prometheus SRE MCP Server. Nothing to install.
get_slo_status 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_slo_status 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_slo_status. 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_slo_status is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-mcp-server). 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 →