asc_get_beta_recruitment_compatible_build_check

GET /v1/betaGroups/{id}/betaRecruitmentCriterionCompatibleBuildCheck — hasCompatibleBuild tells you whether the group currently distributes at least one build that devices matching the recruitment criteria could install. false means public-link joiners who pass the criteria would find NO installa...

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-recruitment-compatible-build-check.md

What asc_get_beta_recruitment_compatible_build_check does on Appstoreconnect Mcp

AI agents call asc_get_beta_recruitment_compatible_build_check 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_recruitment_compatible_build_check is rated Low

This tool performs a read-only query against App Store Connect to check compatibility status. It returns a boolean (hasCompatibleBuild) and has no side effects—it does not create, modify, delete, or execute any operations. The severity is low because misuse would only expose informational metadata about beta testing infrastructure, with no ability to harm data or systems.

From the tool's definition Tool name contains 'get' and description uses 'GET /v1/...' HTTP method. Purpose is to 'tells you whether the group currently distributes' — a query/check operation that retrieves status information about beta build compatibility without modifying any data.

Questions about asc_get_beta_recruitment_compatible_build_check

What does the asc_get_beta_recruitment_compatible_build_check tool do? +

GET /v1/betaGroups/{id}/betaRecruitmentCriterionCompatibleBuildCheck — hasCompatibleBuild tells you whether the group currently distributes at least one build that devices matching the recruitment criteria could install. false means public-link joiners who pass the criteria would find NO installable build — fix the criteria or assign a compatible build before promoting the link. 404s when the group has no criterion at all (observed live) — the check only exists once a criterion does. 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_recruitment_compatible_build_check? +

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

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

Can I rate-limit asc_get_beta_recruitment_compatible_build_check? +

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

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

asc_get_beta_recruitment_compatible_build_check 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.