Get details for a scan run
AI agents call get_scan_run to retrieve information from Trackings 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 and queries data about a previously executed scan run. It has no side effects, does not create, modify, or delete data, and does not trigger new operations. It is a straightforward read operation consistent with the 'Read' category for tools that fetch or retrieve information.
From the tool's definition Tool name 'get_scan_run' and description 'Get details for a scan run' indicate retrieval of existing scan run information without modification or execution of new operations.
Attacks that exploit this kind of access
Get details for a scan run. It is categorised as a Read tool in the Trackings MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trackings MCP Server MCP server in PolicyLayer and add a rule for get_scan_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 Trackings MCP Server. Nothing to install.
get_scan_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_scan_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_scan_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_scan_run is provided by the Trackings MCP Server MCP server (peterw/trackings-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 →