AI agents call app_details to retrieve information from Asc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves information about an app (versions, build status, release state) with no side effects or modifications. Pure read operation.
From the tool's definition Get detailed info about an app including versions, build status, and release state.
Attacks that exploit this kind of access
Get detailed info about an app including versions, build status, and release state. It is categorised as a Read tool in the Asc MCP Server, which means it retrieves data without modifying state.
Register the Asc MCP server in PolicyLayer and add a rule for app_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 Asc. Nothing to install.
app_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_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_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_details is provided by the Asc MCP server (pofky/asc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →