Get only the vulnerable URLs from a batch scan.
AI agents call get_vulnerable_urls 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 and filters results from previously completed batch scans. It queries data without modifying, deleting, or executing any operations. While the server context involves security testing (which could be sensitive), this specific tool merely extracts information from scan results that have already been generated.
From the tool's definition Tool name 'get_vulnerable_urls' and description 'Get only the vulnerable URLs from a batch scan' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Get only the vulnerable URLs from a batch scan. 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_vulnerable_urls: 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_vulnerable_urls 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_vulnerable_urls 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_vulnerable_urls. 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_vulnerable_urls 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 →