Get application run details
AI agents call get_app_run to retrieve information from Dust MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries application run information with no side effects. It falls squarely in the Read category. Severity is low because retrieving run details has minimal blast radius—an agent cannot cause harm by fetching this metadata, assuming the data itself is not sensitive. Confidence is high given the clear 'get' semantics and consistent context with other read-only tools.
From the tool's definition Tool name 'get_app_run' and description 'Get application run details' indicate data retrieval without modification. The verb 'get' and context of querying application run state aligns with read-only operations.
Attacks that exploit this kind of access
Get application run details. It is categorised as a Read tool in the Dust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dust MCP Server MCP server in PolicyLayer and add a rule for get_app_run: 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 Dust MCP Server. Nothing to install.
get_app_run 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 get_app_run 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 get_app_run. 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.
get_app_run is provided by the Dust MCP Server MCP server (ma3u/dust-mcp-server-postman-railway). 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 →