pipeline_webhook_replay_delivery
Re-run a logged delivery
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/pipeline-webhook-replay-delivery.md
What pipeline_webhook_replay_delivery does on Max MCP Server
AI agents invoke pipeline_webhook_replay_delivery to trigger actions in Max 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 pipeline_webhook_replay_delivery is rated High
Replaying webhook deliveries executes external operations with side effects dependent on webhook target and payload.
From the tool's definition Re-run a logged delivery; replay indicates triggering external webhook operations
Attacks that exploit this kind of access
The rule that runs pipeline_webhook_replay_delivery safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipeline_webhook_replay_delivery, this is the rule to start with:
pipeline_webhook_replay_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every pipeline_webhook_replay_delivery call is checked against it from then on.
Questions about pipeline_webhook_replay_delivery
Re-run a logged delivery. It is categorised as a Execute tool in the Max MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for pipeline_webhook_replay_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 Max MCP Server. Nothing to install.
pipeline_webhook_replay_delivery 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 pipeline_webhook_replay_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.
Set action: deny in the PolicyLayer policy for pipeline_webhook_replay_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.
pipeline_webhook_replay_delivery is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue