Retrieve a previous batch scan result by ID.
AI agents call get_batch_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 modifying, deleting, or executing any operations. It is a straightforward read operation that queries a database or cache for existing batch scan data. While the server as a whole facilitates security testing for SQL injection vulnerabilities, this specific tool only retrieves results and has no capability to modify state or trigger new scans.
From the tool's definition The tool name and description indicate retrieval of existing data: 'Retrieve a previous batch scan result by ID.' This is a query operation with no side effects.
Attacks that exploit this kind of access
Retrieve a previous batch 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_batch_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_batch_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_batch_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_batch_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_batch_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 →