util_sla_breach_count
Count SLA breaches in a latency sample against a millisecond threshold.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-sla-breach-count.md
What util_sla_breach_count does on Delx Mcp A2a
AI agents call util_sla_breach_count to retrieve information from Delx Mcp A2a 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 |
|---|---|---|---|
sla_ms | number | Yes | SLA latency threshold in milliseconds. |
samples_ms | array | Yes | Latency samples in milliseconds to count SLA breaches. |
Parameters from the server's own tool schema.
Why util_sla_breach_count is rated Low
Even though util_sla_breach_count only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs util_sla_breach_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_sla_breach_count, this is the rule to start with:
util_sla_breach_count 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 Delx Mcp A2a, apply this rule, and every util_sla_breach_count call is checked against it from then on.
Questions about util_sla_breach_count
Count SLA breaches in a latency sample against a millisecond threshold. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_sla_breach_count accepts 2 parameters: sla_ms, samples_ms. Required: sla_ms, samples_ms. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_sla_breach_count: 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 Delx Mcp A2a. Nothing to install.
util_sla_breach_count 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 util_sla_breach_count 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 util_sla_breach_count. 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.
util_sla_breach_count is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue