SQL Injection 취약점이 있는지 검사
AI agents call scan-injection to retrieve information from Security Scanner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs vulnerability detection analysis on code to identify SQL injection flaws. It reads and analyzes code artifacts to report security issues, with no side effects on data or systems. While the results could inform dangerous actions, the tool itself only retrieves and reports vulnerability information, making it a Read operation.
From the tool's definition Tool name 'scan-injection' and description 'SQL Injection 취약점이 있는지 검사' (checks for SQL injection vulnerabilities). The tool inspects code for vulnerabilities without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
SQL Injection 취약점이 있는지 검사. It is categorised as a Read tool in the Security Scanner MCP MCP Server, which means it retrieves data without modifying state.
Register the Security Scanner MCP server in PolicyLayer and add a rule for scan-injection: 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. Nothing to install.
scan-injection 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 scan-injection 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 scan-injection. 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.
scan-injection is provided by the Security Scanner MCP server (ongjin/security-scanner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
scan-injection is one line of Security Scanner's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →