asc_post_app_event

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-app-event.md

WHAT IT DOES

What asc_post_app_event does on Appstoreconnect Mcp

AI agents use asc_post_app_event 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.

RISK

Why asc_post_app_event is rated Medium

This tool creates new app events in a draft state, which is a reversible write operation. While it can configure app-facing content (badge, deepLink, purchaseRequirement, etc.), the impact is limited because events are created in DRAFT status and can be deleted or modified. This is less severe than Destructive (no irreversible deletion) or Execute (no arbitrary code execution).

From the tool's definition Tool description states 'Create an AppEvent on an app' and 'New events land in DRAFT'. The word 'Create' indicates data creation; events are created in a draft state, which is reversible (can be deleted or modified before submission).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs asc_post_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_post_app_event, this is the rule to start with:

asc_post_app_event Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "asc_post_app_event": {
      "limits": [
        {
          "counter": "asc_post_app_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_post_app_event call is checked against it from then on.

FAQ

Questions about asc_post_app_event

What does the asc_post_app_event tool do? +

Create an AppEvent on an app. Required: appId + referenceName (internal-only, NOT customer-facing — set per-locale name via asc_post_app_event_localization). Optional: badge, deepLink, purchaseRequirement, primaryLocale, priority, purpose, territorySchedules. New events land in DRAFT. Add localizations + screenshots + video clips before submitting for review. 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.

How do I enforce a policy on asc_post_app_event? +

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

What risk level is asc_post_app_event? +

asc_post_app_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit asc_post_app_event? +

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

How do I block asc_post_app_event completely? +

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

What MCP server provides asc_post_app_event? +

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

KEEP EXPLORING

More on Appstoreconnect, and thousands of servers like it.

This server

All 278 Appstoreconnect tools →

Across the catalogue

team_manager_post_blackboard on Team Manager MCP →calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →