list_webhook_deliveries

List recent delivery attempts for a webhook subscription.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/list-webhook-deliveries.md

WHAT IT DOES

What list_webhook_deliveries does on Starfield

AI agents call list_webhook_deliveries 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
`page`	number	—	Page number
`limit`	number	—	Results per page (default 25)

Parameters from the server's own tool schema.

RISK

Why list_webhook_deliveries is rated Low

Even though list_webhook_deliveries 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 list_webhook_deliveries 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 list_webhook_deliveries, this is the rule to start with:

list_webhook_deliveries Allowed

list_webhook_deliveries 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": {
    "list_webhook_deliveries": {}
  }
}

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 list_webhook_deliveries call is checked against it from then on.

FAQ

Questions about list_webhook_deliveries

What does the list_webhook_deliveries tool do? +

List recent delivery attempts for a webhook subscription. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does list_webhook_deliveries accept? +

list_webhook_deliveries accepts 3 parameters: id, page, limit. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_webhook_deliveries? +

Register the Starfield MCP server in PolicyLayer and add a rule for list_webhook_deliveries: 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 list_webhook_deliveries? +

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

Can I rate-limit list_webhook_deliveries? +

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

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

list_webhook_deliveries 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_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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