List all previous security scans.
AI agents call list_scans 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 performs a simple query/list operation to enumerate past security scan records. It is read-only and has no destructive, execute, or financial implications. Even though it provides access to security scan history (which could contain sensitive vulnerability information), the operation itself is purely informational retrieval with no capability to alter or act upon that data.
From the tool's definition The tool name 'list_scans' combined with the description 'List all previous security scans' indicates a data retrieval operation with no side effects. It retrieves historical scan information without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
List all previous security scans. 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 list_scans: 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.
list_scans 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 list_scans 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 list_scans. 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.
list_scans 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 →