replay_connection_delivery

Re-arm ONE dead delivery so the pump tries it again — the escape hatch for \

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/replay-connection-delivery.md

WHAT IT DOES

What replay_connection_delivery does on ProAgentStore

AI agents invoke replay_connection_delivery to trigger actions in ProAgentStore. 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.

RISK

Why replay_connection_delivery is rated High

Triggers a retry of a failed delivery, executing an external operation again.

From the tool's definition Re-arm ONE dead delivery so the pump tries it again

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs replay_connection_delivery safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replay_connection_delivery, this is the rule to start with:

replay_connection_delivery Rate-limited

replay_connection_delivery 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "replay_connection_delivery": {
      "limits": [
        {
          "counter": "replay_connection_delivery_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every replay_connection_delivery call is checked against it from then on.

FAQ

Questions about replay_connection_delivery

What does the replay_connection_delivery tool do? +

Re-arm ONE dead delivery so the pump tries it again — the escape hatch for \. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on replay_connection_delivery? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for replay_connection_delivery: 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 ProAgentStore. Nothing to install.

What risk level is replay_connection_delivery? +

replay_connection_delivery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit replay_connection_delivery? +

Yes. Add a rate_limit block to the replay_connection_delivery 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.

How do I block replay_connection_delivery completely? +

Set action: deny in the PolicyLayer policy for replay_connection_delivery. 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.

What MCP server provides replay_connection_delivery? +

replay_connection_delivery is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →