asc_get_marketplace_search_detail
GET /v1/apps/{id}/marketplaceSearchDetail — the catalogUrl for a MARKETPLACE app (alternative app store). Observed live: calling this on a NON-marketplace app returns an Apple-side 500 UNEXPECTED_ERROR rather than a clean 404 — that 500 means
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-marketplace-search-detail.md
What asc_get_marketplace_search_detail does on Appstoreconnect Mcp
AI agents call asc_get_marketplace_search_detail 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_marketplace_search_detail is rated Low
This tool retrieves marketplace search detail information without modifying, deleting, or executing any operations. The 500 error behavior on non-marketplace apps is a server-side issue, not a capability of the tool itself. The blast radius of misuse is minimal—an attacker gains read access to marketplace app metadata, which is not sensitive or system-critical information. Classified as Read with low severity.
From the tool's definition Tool name contains 'get_' and description states 'GET /v1/apps/{id}/marketplaceSearchDetail' — a read-only retrieval operation that queries catalog URL data for marketplace apps.
Attacks that exploit this kind of access
The rule that runs asc_get_marketplace_search_detail 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_marketplace_search_detail, this is the rule to start with:
asc_get_marketplace_search_detail 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_marketplace_search_detail call is checked against it from then on.
Questions about asc_get_marketplace_search_detail
GET /v1/apps/{id}/marketplaceSearchDetail — the catalogUrl for a MARKETPLACE app (alternative app store). Observed live: calling this on a NON-marketplace app returns an Apple-side 500 UNEXPECTED_ERROR rather than a clean 404 — that 500 means. 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_marketplace_search_detail: 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_marketplace_search_detail 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_marketplace_search_detail 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_marketplace_search_detail. 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_marketplace_search_detail 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