replay_webhook_delivery · Thesma MCP Server MCP

WHAT IT DOES

What replay_webhook_delivery does on Thesma MCP Server

AI agents invoke replay_webhook_delivery to trigger actions in Thesma MCP Server. 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.

WHY IT NEEDS A POLICY

Why replay_webhook_delivery needs a policy

The name implies re-executing or re-sending a webhook event, which is an external operation that triggers side effects on downstream systems. This falls under Execute rather than Write because it re-fires an external operation. Severity is high because replaying webhooks could trigger duplicate processing, financial actions, or data mutations in external systems.

From the tool's definition Tool name 'replay_webhook_delivery' suggests re-triggering a past webhook delivery; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replay_webhook_delivery Rate-limited

replay_webhook_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_webhook_delivery": {
      "limits": [
        {
          "counter": "replay_webhook_delivery_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Thesma MCP Server, so you can run agents against it safely.

FAQ

Questions about replay_webhook_delivery

What does the replay_webhook_delivery tool do? +

replay_webhook_delivery. It is categorised as a Execute tool in the Thesma MCP Server 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_webhook_delivery? +

Register the Thesma MCP Server MCP server in PolicyLayer and add a rule for replay_webhook_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 Thesma MCP Server. Nothing to install.

What risk level is replay_webhook_delivery? +

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

Can I rate-limit replay_webhook_delivery? +

Yes. Add a rate_limit block to the replay_webhook_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_webhook_delivery completely? +

Set action: deny in the PolicyLayer policy for replay_webhook_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_webhook_delivery? +

replay_webhook_delivery is provided by the Thesma MCP Server MCP server (thesma-dev/thesma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.