asc_upload_app_event_screenshot

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-upload-app-event-screenshot.md

WHAT IT DOES

What asc_upload_app_event_screenshot does on Appstoreconnect Mcp

AI agents use asc_upload_app_event_screenshot 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_upload_app_event_screenshot is rated Medium

This tool performs a multi-step write operation that uploads and commits new app event screenshot data to App Store Connect. While it reads from local disk and uploads to external storage, the primary effect is creating and modifying a persistent AppEventScreenshot resource in the App Store Connect system. This is reversible (the tool doesn't delete or destroy), making it Write rather than Destructive or Execute.

From the tool's definition 'Reads localFilePath from disk, reserves an AppEventScreenshot...PUTs every uploadOperation chunk to Apple storage in sequence, then commits with uploaded=true.' The tool creates/modifies data (reserves and commits a screenshot resource) in Apple's App Store…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

asc_upload_app_event_screenshot Rate-limited

asc_upload_app_event_screenshot 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_upload_app_event_screenshot": {
      "limits": [
        {
          "counter": "asc_upload_app_event_screenshot_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_upload_app_event_screenshot call is checked against it from then on.

FAQ

Questions about asc_upload_app_event_screenshot

What does the asc_upload_app_event_screenshot tool do? +

Composite tool. Reads localFilePath from disk, reserves an AppEventScreenshot under the given event localization for the given asset slot (EVENT_CARD / EVENT_DETAILS_PAGE), PUTs every uploadOperation chunk to Apple storage in sequence, then commits with uploaded=true. Returns the committed resource + per-chunk summary. Tilde paths (~/...) are expanded. Note: this resource has NO sourceFileChecksum on the commit step — Apple does not require an MD5 here (unlike v0.13 AppScreenshot). 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_upload_app_event_screenshot? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_upload_app_event_screenshot: 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_upload_app_event_screenshot? +

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

Can I rate-limit asc_upload_app_event_screenshot? +

Yes. Add a rate_limit block to the asc_upload_app_event_screenshot 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_upload_app_event_screenshot completely? +

Set action: deny in the PolicyLayer policy for asc_upload_app_event_screenshot. 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_upload_app_event_screenshot? +

asc_upload_app_event_screenshot 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

calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

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