uptime_sla
Uptime / SLA Downtime Calculator — Allowed downtime per day/week/month/year from an availability 'nines' percent.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/uptime-sla.md
What uptime_sla does on Gateway
AI agents call uptime_sla to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
availability_pct | number | Yes | Availability percent, e.g. 99.9 |
Parameters from the server's own tool schema.
Why uptime_sla is rated Low
This is a pure read/compute tool. It retrieves or calculates static information based on input parameters without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—an agent could only generate incorrect SLA calculations, which would be a business logic error rather than a security incident.
From the tool's definition Tool is a calculator that takes uptime percentage input and returns computed downtime values (per day/week/month/year). No mutation, deletion, execution, or financial transaction occurs—only arithmetic computation and data retrieval.
Attacks that exploit this kind of access
The rule that runs uptime_sla safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uptime_sla, this is the rule to start with:
uptime_sla is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every uptime_sla call is checked against it from then on.
Questions about uptime_sla
Uptime / SLA Downtime Calculator — Allowed downtime per day/week/month/year from an availability 'nines' percent. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
uptime_sla accepts 1 parameter: availability_pct. Required: availability_pct. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for uptime_sla: 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 Gateway. Nothing to install.
uptime_sla 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 uptime_sla 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 uptime_sla. 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.
uptime_sla is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue