asc_list_beta_feedback_screenshot_submissions

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-list-beta-feedback-screenshot-submissions.md

WHAT IT DOES

What asc_list_beta_feedback_screenshot_submissions does on Appstoreconnect Mcp

AI agents call asc_list_beta_feedback_screenshot_submissions 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.

RISK

Why asc_list_beta_feedback_screenshot_submissions is rated Low

This tool retrieves and queries existing data (beta feedback screenshots) without any side effects. It uses a GET endpoint which is inherently read-only. The description explicitly states it 'lists' submissions and filters them, which are characteristic Read operations. There is no capability to create, modify, delete, or execute operations.

From the tool's definition Tool performs a LIST operation via GET request to retrieve TestFlight beta feedback screenshot submissions. Returns data about created dates, devices, OS, comments, screenshots, and linkage information with no modification or deletion capability mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

asc_list_beta_feedback_screenshot_submissions Allowed

asc_list_beta_feedback_screenshot_submissions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "asc_list_beta_feedback_screenshot_submissions": {}
  }
}

ALLOW ONLY 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_list_beta_feedback_screenshot_submissions call is checked against it from then on.

FAQ

Questions about asc_list_beta_feedback_screenshot_submissions

What does the asc_list_beta_feedback_screenshot_submissions tool do? +

List screenshot feedback testers sent from TestFlight via GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions. Each row shows created date, device, OS, comment preview, screenshot count, and build/tester linkage. Filter by build to triage feedback per release (. 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_list_beta_feedback_screenshot_submissions? +

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

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

Can I rate-limit asc_list_beta_feedback_screenshot_submissions? +

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

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

asc_list_beta_feedback_screenshot_submissions 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server →browser_screenshot on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →