asc_get_webhook

GET /v1/webhooks/{id} — one webhook with its app relationship. The secret is write-only and never returned. For delivery history use asc_list_webhook_deliveries.

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-webhook.md

What asc_get_webhook does on Appstoreconnect Mcp

AI agents call asc_get_webhook 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_get_webhook is rated Low

This tool retrieves webhook configuration metadata without modification. It performs a GET request to fetch a single webhook resource and its relationships. No data is created, modified, deleted, or executed. The confirmation that secrets are never returned reinforces the read-only nature. This poses minimal risk as it only exposes existing webhook metadata.

From the tool's definition Tool name starts with 'asc_get_' and description explicitly states 'GET /v1/webhooks/{id}' indicating a retrieval operation. Description further clarifies 'The secret is write-only and never returned', confirming this is read-only access.

Questions about asc_get_webhook

What does the asc_get_webhook tool do? +

GET /v1/webhooks/{id} — one webhook with its app relationship. The secret is write-only and never returned. For delivery history use asc_list_webhook_deliveries. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on asc_get_webhook? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_get_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.

What risk level is asc_get_webhook? +

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

Can I rate-limit asc_get_webhook? +

Yes. Add a rate_limit block to the asc_get_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.

How do I block asc_get_webhook completely? +

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

What MCP server provides asc_get_webhook? +

asc_get_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.