Retrieve results from a previous scan.
AI agents call get_scan_results to retrieve information from Security Scanner MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data from completed scans without modifying, deleting, executing new operations, or committing financial actions. The blast radius of misuse is minimal: an attacker could access scan results already generated, potentially revealing information about infrastructure vulnerabilities, but cannot directly harm systems or trigger new scans. It is a standard Read operation.
From the tool's definition Tool description states 'Retrieve results from a previous scan' — a pure retrieval operation with no side effects on the scanning infrastructure or findings.
Attacks that exploit this kind of access
Retrieve results from a previous scan. It is categorised as a Read tool in the Security Scanner MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Security Scanner MCP Server MCP server in PolicyLayer and add a rule for get_scan_results: 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 Security Scanner MCP Server. Nothing to install.
get_scan_results 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_results 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_results. 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_results is provided by the Security Scanner MCP Server MCP server (marc-shade/security-scanner-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 →