scan_code_vulnerabilities

Escanea el código fuente del proyecto buscando patrones de código vulnerable como XSS, eval(), innerHTML sin sanitizar, tokens en localStorage, etc. Retorna vulnerabilidades con ubicación exacta y soluciones.

Server MCP Security Scanner jmitac/mcp-security-scanner
Category Read
Risk class Low
Parameters 00 required

What scan_code_vulnerabilities does on MCP Security Scanner

AI agents call scan_code_vulnerabilities to retrieve information from MCP Security Scanner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why scan_code_vulnerabilities needs a policy

This tool performs static code analysis by examining source code for security vulnerabilities (XSS, eval, innerHTML, tokens in localStorage). It is a read-only operation that queries and retrieves vulnerability information without modifying the codebase or executing external operations.

From the tool's definition Tool description states it 'Escanea' (scans) the code searching for vulnerable patterns and 'Retorna vulnerabilidades' (returns vulnerabilities) with exact location and solutions.

Questions about scan_code_vulnerabilities

What does the scan_code_vulnerabilities tool do? +

Escanea el código fuente del proyecto buscando patrones de código vulnerable como XSS, eval(), innerHTML sin sanitizar, tokens en localStorage, etc. Retorna vulnerabilidades con ubicación exacta y soluciones. It is categorised as a Read tool in the MCP Security Scanner MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scan_code_vulnerabilities? +

Register the MCP Security Scanner MCP server in PolicyLayer and add a rule for scan_code_vulnerabilities: 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 MCP Security Scanner. Nothing to install.

What risk level is scan_code_vulnerabilities? +

scan_code_vulnerabilities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit scan_code_vulnerabilities? +

Yes. Add a rate_limit block to the scan_code_vulnerabilities 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.

How do I block scan_code_vulnerabilities completely? +

Set action: deny in the PolicyLayer policy for scan_code_vulnerabilities. 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.

What MCP server provides scan_code_vulnerabilities? +

scan_code_vulnerabilities is provided by the MCP Security Scanner MCP server (jmitac/mcp-security-scanner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.