retry_backoff
Retry Backoff Schedule — Exponential backoff delays per attempt with optional jitter and per-attempt cap.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/retry-backoff.md
What retry_backoff does on Gateway
AI agents invoke retry_backoff to trigger actions in Gateway. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
factor | number | — | Backoff multiplier (default 2) |
attempts | integer | Yes | Number of attempts 1..50 |
max_delay | number | — | Cap per-attempt delay (seconds) |
base_delay | number | Yes | Base delay seconds |
Parameters from the server's own tool schema.
Why retry_backoff is rated High
A retry backoff scheduler actively controls execution flow by calculating delays and scheduling retry attempts. It is more than a pure read/calculate tool because it governs when operations are re-executed. Closest to Execute given it triggers or governs external operational timing, though it may primarily be a calculator; confidence is moderate since the description could imply pure calculation.
From the tool's definition 'Retry Backoff Schedule — Exponential backoff delays per attempt with optional jitter and per-attempt cap' — this tool computes and applies a retry scheduling mechanism, triggering timed execution attempts
Attacks that exploit this kind of access
The rule that runs retry_backoff 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 retry_backoff, this is the rule to start with:
retry_backoff stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 retry_backoff call is checked against it from then on.
Questions about retry_backoff
Retry Backoff Schedule — Exponential backoff delays per attempt with optional jitter and per-attempt cap. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
retry_backoff accepts 4 parameters: factor, attempts, max_delay, base_delay. Required: attempts, base_delay. 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 retry_backoff: 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.
retry_backoff is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the retry_backoff 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 retry_backoff. 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.
retry_backoff 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.
Across the catalogue