AI agents call scan_dependencies to retrieve information from Secscan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The scan_dependencies tool performs static analysis on dependency metadata (lockfiles, manifests) to identify known vulnerabilities. This is a read operation: it retrieves and analyzes existing data without creating, modifying, deleting, executing code, or triggering external operations.
From the tool's definition Tool description states it 'scan[s] lockfiles and manifests for known vulnerable dependencies' — a read-only operation that queries dependency files against vulnerability databases without modifying code, infrastructure, or system state.
Attacks that exploit this kind of access
Scan lockfiles and manifests for known vulnerable dependencies (SCA). It is categorised as a Read tool in the Secscan MCP Server, which means it retrieves data without modifying state.
Register the Secscan MCP server in PolicyLayer and add a rule for scan_dependencies: 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 Secscan. Nothing to install.
scan_dependencies 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_dependencies 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_dependencies. 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_dependencies is provided by the Secscan MCP server (openjkai/secscan_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
scan_dependencies is one line of Secscan'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 →