Get detailed information about an App Store app. Returns an object with:\n
AI agents call app-store-details to retrieve information from App Market Intelligence MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available app metadata from the Apple App Store. It performs no side effects, creates no resources, executes no code, and modifies no data. It is a straightforward data retrieval operation consistent with the 'Read' category. Low severity due to minimal blast radius—misuse would only result in retrieving existing public information.
From the tool's definition Tool name 'app-store-details' and description indicate it 'Get detailed information about an App Store app' with read-only data retrieval ('Returns an object with'). No mutation, deletion, execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access app-store-details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and App Market Intelligence MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for app-store-details:
{
"version": "1",
"default": "deny",
"tools": {
"app-store-details": {}
}
}app-store-details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about an App Store app. Returns an object with:\n. It is categorised as a Read tool in the App Market Intelligence MCP MCP Server, which means it retrieves data without modifying state.
Register the App Market Intelligence MCP server in PolicyLayer and add a rule for app-store-details: 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 App Market Intelligence MCP. Nothing to install.
app-store-details 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 app-store-details 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 app-store-details. 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.
app-store-details is provided by the App Market Intelligence MCP server (jiantaofu/appinsightmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from App Market Intelligence MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 App Market Intelligence MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.