List all past scans with their severity scores and targets.
AI agents call get_scan_history to retrieve information from Mcp Safeguard 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 existing scan history data. It performs a read-only operation returning past scan records with metadata (severity scores, targets). There is no creation, modification, deletion, code execution, or financial impact. The severity is low as exposure of scan history poses minimal risk—it is informational data about prior security assessments, not operational data or credentials.
From the tool's definition Tool name 'get_scan_history' and description 'List all past scans' indicate retrieval of historical scan data without modification. No side effects or operations mentioned.
Attacks that exploit this kind of access
List all past scans with their severity scores and targets. It is categorised as a Read tool in the Mcp Safeguard MCP Server, which means it retrieves data without modifying state.
Register the Mcp Safeguard MCP server in PolicyLayer and add a rule for get_scan_history: 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 Mcp Safeguard. Nothing to install.
get_scan_history 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_history 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_history. 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_history is provided by the Mcp Safeguard MCP server (syedanas01/mcp-safeguard). 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 →