asc_list_webhook_deliveries
GET /v1/webhooks/{id}/deliveries — per-attempt delivery records: state (SUCCEEDED / FAILED / PENDING), event type, sent date, response HTTP status, error message, and whether the attempt was a redelivery. Filter by state and createdDate window to find failures (
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-webhook-deliveries.md
What asc_list_webhook_deliveries does on Appstoreconnect Mcp
AI agents call asc_list_webhook_deliveries to retrieve information from Appstoreconnect Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why asc_list_webhook_deliveries is rated Low
This tool retrieves historical webhook delivery attempt records for inspection and filtering. It performs no write, delete, or execute operations—it only queries metadata about past webhook deliveries. The blast radius of misuse is minimal; an agent could retrieve sensitive event information or delivery details but cannot alter system state or trigger actions.
From the tool's definition Tool name includes 'list' and description emphasizes retrieval of delivery records (state, event type, sent date, response status, etc.) without modification. The HTTP method is explicitly GET. Filter capability suggests querying/searching existing data.
Attacks that exploit this kind of access
The rule that runs asc_list_webhook_deliveries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appstoreconnect Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For asc_list_webhook_deliveries, this is the rule to start with:
asc_list_webhook_deliveries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_list_webhook_deliveries call is checked against it from then on.
Questions about asc_list_webhook_deliveries
GET /v1/webhooks/{id}/deliveries — per-attempt delivery records: state (SUCCEEDED / FAILED / PENDING), event type, sent date, response HTTP status, error message, and whether the attempt was a redelivery. Filter by state and createdDate window to find failures (. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_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 Appstoreconnect Mcp. Nothing to install.
asc_list_webhook_deliveries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asc_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.
Set action: deny in the PolicyLayer policy for asc_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.
asc_list_webhook_deliveries is provided by the Appstoreconnect MCP server (@akoskomuves/appstoreconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appstoreconnect, and thousands of servers like it.
This server
Across the catalogue