asc_get_app_event
Fetch a single AppEvent by ID with its localizations expanded. Returns the full attribute surface including territorySchedules (writable per-territory schedule entries) and archivedTerritorySchedules (read-only history).
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-app-event.md
What asc_get_app_event does on Appstoreconnect Mcp
AI agents call asc_get_app_event 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_app_event is rated Low
This tool retrieves a single AppEvent resource by ID and returns its full attributes including localizations and schedule information. Despite the presence of writable fields in the returned data structure, the tool itself performs only a read operation (fetch) with no side effects or modifications. It falls clearly into the Read category.
From the tool's definition Tool description uses 'Fetch' and 'Returns', indicating data retrieval with no modification. The mention of 'territorySchedules (writable per-territory schedule entries)' refers to data structure attributes being returned, not actions performed by this tool.
Attacks that exploit this kind of access
The rule that runs asc_get_app_event 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_get_app_event, this is the rule to start with:
asc_get_app_event 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_get_app_event call is checked against it from then on.
Questions about asc_get_app_event
Fetch a single AppEvent by ID with its localizations expanded. Returns the full attribute surface including territorySchedules (writable per-territory schedule entries) and archivedTerritorySchedules (read-only history). 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_get_app_event: 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_get_app_event 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_get_app_event 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_get_app_event. 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_get_app_event 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