Retrieve a previous scan result by ID.
AI agents call get_scan_result to retrieve information from SQL Injection 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 previously stored scan results without creating, modifying, or deleting data. While the scan results may contain sensitive information about vulnerabilities discovered in target systems (which elevates severity from low to medium due to potential information disclosure risks), the tool itself performs only a read operation.
From the tool's definition Tool name 'get_scan_result' and description 'Retrieve a previous scan result by ID' indicate a read operation that queries and returns data without modifying it.
Attacks that exploit this kind of access
Retrieve a previous scan result by ID. It is categorised as a Read tool in the SQL Injection MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQL Injection MCP Server MCP server in PolicyLayer and add a rule for get_scan_result: 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 SQL Injection MCP Server. Nothing to install.
get_scan_result 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_result 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_result. 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_result is provided by the SQL Injection MCP Server MCP server (vivashu27/sqlinjector_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 →