코드에서 보안 취약점을 검사합니다 (시크릿, SQL Injection, XSS 등)
AI agents call scan-security 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 static analysis and vulnerability detection without executing code, modifying data, or triggering external operations. It retrieves and reports security findings, which is a Read operation. The low severity reflects that misuse would only surface incorrect scan results, not compromise actual systems or data.
From the tool's definition Tool name 'scan-security' and description state it '검사합니다' (checks/scans) code for vulnerabilities. The server description confirms it 'Automatically detects security vulnerabilities' and 'scanning for' issues.
Attacks that exploit this kind of access
코드에서 보안 취약점을 검사합니다 (시크릿, SQL Injection, XSS 등). 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-security: 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-security 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-security 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-security. 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-security 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.
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 →