Escanea el código fuente buscando secrets expuestos como API keys, tokens, contraseñas hardcodeadas, claves privadas, connection strings de bases de datos, etc.
AI agents call scan_secrets 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.
This is a security scanning tool that retrieves and analyzes code to detect secrets. It has no side effects—it only reads and reports findings. While the discovery of secrets could inform subsequent high-risk actions, the tool itself is purely informational. No data is modified, executed, or deleted.
From the tool's definition Tool performs scanning and detection ('Escanea el código fuente buscando') of exposed secrets without modifying, executing, or deleting any code or infrastructure. It reads source code to identify vulnerabilities.
Attacks that exploit this kind of access
Escanea el código fuente buscando secrets expuestos como API keys, tokens, contraseñas hardcodeadas, claves privadas, connection strings de bases de datos, etc. It is categorised as a Read tool in the MCP Security Scanner MCP Server, which means it retrieves data without modifying state.
Register the MCP Security Scanner MCP server in PolicyLayer and add a rule for scan_secrets: 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.
scan_secrets 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_secrets 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_secrets. 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_secrets 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.
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 →