asc_get_beta_feedback_screenshot_submission

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-get-beta-feedback-screenshot-submission.md

WHAT IT DOES

What asc_get_beta_feedback_screenshot_submission does on Appstoreconnect Mcp

AI agents call asc_get_beta_feedback_screenshot_submission 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_get_beta_feedback_screenshot_submission is rated Low

This tool retrieves and queries existing beta feedback screenshot data with metadata (device context, screenshots array). It performs no mutations, deletions, or side effects—only data retrieval with temporary signed download URLs. The refresh mechanism for expired URLs is a read operation, not a write. This is a straightforward Read category tool with low severity due to limited blast radius if misused.

From the tool's definition Fetch one screenshot feedback submission... The URLs are time-limited Apple-signed download links; if one has expired, re-run this tool for fresh URLs.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

asc_get_beta_feedback_screenshot_submission Allowed

asc_get_beta_feedback_screenshot_submission 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_get_beta_feedback_screenshot_submission": {}
  }
}

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

FAQ

Questions about asc_get_beta_feedback_screenshot_submission

What does the asc_get_beta_feedback_screenshot_submission tool do? +

Fetch one screenshot feedback submission with full device context (connection type, battery, disk, uptime, screen size) and the screenshots array — each entry carries url + width + height + expirationDate. The URLs are time-limited Apple-signed download links; if one has expired, re-run this tool for fresh URLs. include=build,tester for triage context. 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_get_beta_feedback_screenshot_submission? +

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

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

Can I rate-limit asc_get_beta_feedback_screenshot_submission? +

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

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

asc_get_beta_feedback_screenshot_submission 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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