AI agents call check_dependencies to retrieve information from Codescan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The check_dependencies tool performs informational queries on a codebase's dependency metadata and configuration files. It generates reports about dependency status (outdated signals, duplicates, missing files) but does not create, modify, or delete any data. This is a classic Read operation: it retrieves and examines existing project state to provide analysis, with no side effects or state changes.
From the tool's definition Tool analyzes and counts project dependencies, checks for outdated signals, duplicate lockfiles, and missing lockfiles.
Attacks that exploit this kind of access
Analyze project dependencies: count, outdated signals, duplicate lockfiles, missing lockfiles. It is categorised as a Read tool in the Codescan MCP Server, which means it retrieves data without modifying state.
Register the Codescan MCP server in PolicyLayer and add a rule for check_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 Codescan. Nothing to install.
check_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 check_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 check_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.
check_dependencies is provided by the Codescan MCP server (yifanyifan897645/codescan-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 →