Scan the project for dependency vulnerabilities.
AI agents call scan_dependencies to retrieve information from Security-Use MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs vulnerability scanning and analysis of project dependencies, which is fundamentally a read operation. It queries project metadata and compares against vulnerability databases to identify issues, but produces no side effects, modifications, or state changes.
From the tool's definition Tool description states 'Scan the project for dependency vulnerabilities' - scanning is a read-only operation that retrieves and analyzes information about dependencies without modifying them.
Attacks that exploit this kind of access
Scan the project for dependency vulnerabilities. It is categorised as a Read tool in the Security-Use MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Security-Use MCP Server 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 Security-Use MCP Server. 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 Security-Use MCP Server MCP server (security-use/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 →