Audit the full transitive dependency tree of a package. Crawls all nested dependencies recursively and aggregates vulnerabilities across the entire graph. Use when you need to know the total attack surface, not just direct deps.
AI agents call depguard_audit_deep to retrieve information from Depguard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes dependency trees, crawling and aggregating vulnerability information without modifying, executing, or deleting anything. It is a deep inspection/query operation. Medium severity because it processes potentially sensitive dependency and vulnerability data across an entire graph, but has no destructive or write side effects.
From the tool's definition Audit the full transitive dependency tree of a package. Crawls all nested dependencies recursively and aggregates vulnerabilities
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access depguard_audit_deep gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Depguard, and nothing reaches the server without passing your rules. This is the rule we recommend for depguard_audit_deep:
{
"version": "1",
"default": "deny",
"tools": {
"depguard_audit_deep": {}
}
}depguard_audit_deep is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Audit the full transitive dependency tree of a package. Crawls all nested dependencies recursively and aggregates vulnerabilities across the entire graph. Use when you need to know the total attack surface, not just direct deps. It is categorised as a Read tool in the Depguard MCP Server, which means it retrieves data without modifying state.
Register the Depguard MCP server in PolicyLayer and add a rule for depguard_audit_deep: 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 Depguard. Nothing to install.
depguard_audit_deep 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 depguard_audit_deep 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 depguard_audit_deep. 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.
depguard_audit_deep is provided by the Depguard MCP server (mopanc/depguard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Depguard, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Depguard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.