AI agents call monitoring_sla_status to retrieve information from Infra Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or derives metrics from monitoring data (uptime percentage) to compute SLA status and allowed downtime. It performs calculations and reporting on existing data with no side effects, reversible changes, code execution, data destruction, or financial impact. The operation is purely informational and read-only in nature.
From the tool's definition Tool name 'monitoring_sla_status' and description 'Calculate SLA status and allowed downtime based on uptime percentage' indicate a retrieval and calculation operation that queries monitoring data to compute SLA metrics.
Attacks that exploit this kind of access
Calculate SLA status and allowed downtime based on uptime percentage. It is categorised as a Read tool in the Infra Ops MCP Server, which means it retrieves data without modifying state.
Register the Infra Ops MCP server in PolicyLayer and add a rule for monitoring_sla_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 Infra Ops. Nothing to install.
monitoring_sla_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 monitoring_sla_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 monitoring_sla_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.
monitoring_sla_status is provided by the Infra Ops MCP server (skyvanguard/infra-ops-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 →