asc_get_beta_tester
Fetch a single beta tester with relationships expanded (apps + betaGroups + builds). Use to inspect which groups and apps a tester has been onboarded to before changing membership.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-beta-tester.md
What asc_get_beta_tester does on Appstoreconnect Mcp
AI agents call asc_get_beta_tester 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.
Why asc_get_beta_tester is rated Low
This tool retrieves and queries beta tester information with expanded relationships. It performs no side effects, creates no data, executes no code, and makes no changes to the system. The intended use case is inspection before taking action elsewhere, which is characteristic of Read category tools.
From the tool's definition Tool description explicitly states 'Fetch a single beta tester' and 'Use to inspect which groups and apps a tester has been onboarded to' — these are read-only operations with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs asc_get_beta_tester 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_tester, this is the rule to start with:
asc_get_beta_tester is read-only, so it stays allowed. 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_get_beta_tester call is checked against it from then on.
Questions about asc_get_beta_tester
Fetch a single beta tester with relationships expanded (apps + betaGroups + builds). Use to inspect which groups and apps a tester has been onboarded to before changing membership. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_get_beta_tester: 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_get_beta_tester is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asc_get_beta_tester 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_get_beta_tester. 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_get_beta_tester 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