asc_post_webhook
POST /v1/webhooks — register an HTTPS endpoint to receive App Store Connect event notifications for ONE app. ALL FIVE attributes are required: name, url (HTTPS), secret (HMAC-SHA256 signing key — store it on the receiving side first; it is write-only and never readable back), eventTypes (at least...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-webhook.md
What asc_post_webhook does on Appstoreconnect Mcp
AI agents use asc_post_webhook to create or update resources in Appstoreconnect Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appstoreconnect Mcp environment.
Why asc_post_webhook is rated Medium
The tool creates a new webhook registration in App Store Connect, which is a reversible write operation. While webhooks can trigger external notifications and the secret material is sensitive, the operation itself is reversible (webhooks can be deleted/disabled).
From the tool's definition Tool description states 'POST /v1/webhooks — register an HTTPS endpoint' and 'After creating, verify the endpoint', indicating creation of a new webhook resource. This is a write/create operation that modifies App Store Connect configuration.
Attacks that exploit this kind of access
The rule that runs asc_post_webhook 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_post_webhook, this is the rule to start with:
asc_post_webhook stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_post_webhook call is checked against it from then on.
Questions about asc_post_webhook
POST /v1/webhooks — register an HTTPS endpoint to receive App Store Connect event notifications for ONE app. ALL FIVE attributes are required: name, url (HTTPS), secret (HMAC-SHA256 signing key — store it on the receiving side first; it is write-only and never readable back), eventTypes (at least one of the 12), enabled. After creating, verify the endpoint with asc_post_webhook_ping. Useful pairing: BETA_FEEDBACK_*_CREATED events + the v0.16 asc_list_beta_feedback_* read tools. It is categorised as a Write tool in the Appstoreconnect Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_webhook: 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_post_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the asc_post_webhook 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_post_webhook. 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_post_webhook 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