asc_post_review_submission_item
Add an App Store version as an item under a draft review submission. The parent submission must be in READY_FOR_REVIEW state (drafts only — once submitted, the item set is frozen). One item per call.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-review-submission-item.md
What asc_post_review_submission_item does on Appstoreconnect Mcp
AI agents use asc_post_review_submission_item 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_review_submission_item is rated Medium
This tool creates/adds new items to a draft review submission, which is a reversible data modification operation. It does not execute code, delete data irreversibly, or move money. The medium severity reflects that misuse could add incorrect app versions to review submissions, requiring manual correction, but the impact is contained to draft state (not yet submitted) and is reversible by removing the item.
From the tool's definition Tool description uses 'Add an App Store version as an item', which is a create operation that modifies a draft review submission by adding items to it.
Attacks that exploit this kind of access
The rule that runs asc_post_review_submission_item 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_review_submission_item, this is the rule to start with:
asc_post_review_submission_item 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_review_submission_item call is checked against it from then on.
Questions about asc_post_review_submission_item
Add an App Store version as an item under a draft review submission. The parent submission must be in READY_FOR_REVIEW state (drafts only — once submitted, the item set is frozen). One item per call. 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_review_submission_item: 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_review_submission_item 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_review_submission_item 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_review_submission_item. 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_review_submission_item 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