Check the health and connectivity of the observability stack (Loki, Prometheus, Grafana).
AI agents call check_stack_status to retrieve information from Observability MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic querying of observability stack health without modifying, executing external commands, deleting data, or moving money. It retrieves and reports the current state of monitoring infrastructure components, which is a safe informational read operation with minimal blast radius if misused.
From the tool's definition check_stack_status checks health and connectivity of observability components (Loki, Prometheus, Grafana), which is a read-only status query operation with no side effects.
Attacks that exploit this kind of access
Check the health and connectivity of the observability stack (Loki, Prometheus, Grafana). It is categorised as a Read tool in the Observability MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Observability MCP Server MCP server in PolicyLayer and add a rule for check_stack_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 Observability MCP Server. Nothing to install.
check_stack_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 check_stack_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 check_stack_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.
check_stack_status is provided by the Observability MCP Server MCP server (sandraschi/observability-mcp). 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 →