replay_webhook_delivery

Replay a failed or previous webhook delivery.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/replay-webhook-delivery.md

WHAT IT DOES

What replay_webhook_delivery does on Starfield

AI agents call replay_webhook_delivery to retrieve information from Starfield 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
`id`	string	Yes	Webhook subscription ID
`deliveryId`	string	Yes	Webhook delivery ID

Parameters from the server's own tool schema.

RISK

Why replay_webhook_delivery is rated Low

Even though replay_webhook_delivery 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

RECOMMENDED RULE

The rule that runs replay_webhook_delivery safely

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

replay_webhook_delivery Allowed

replay_webhook_delivery is read-only, so it stays allowed. 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": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about replay_webhook_delivery

What does the replay_webhook_delivery tool do? +

Replay a failed or previous webhook delivery. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does replay_webhook_delivery accept? +

replay_webhook_delivery accepts 2 parameters: id, deliveryId. Required: id, deliveryId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on replay_webhook_delivery? +

Register the Starfield 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 Starfield. Nothing to install.

What risk level is replay_webhook_delivery? +

replay_webhook_delivery is a Read tool with low risk. Read-only tools are generally safe to allow by default.

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 Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

aiva_get_delivery_schedule on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →