Audit ALL dependencies in a project at once. Scans direct deps (full audit), transitive deps from lock file (vulnerability check), and the packageManager field. Pass the path to package.json and get a consolidated security report. Use this when the user asks to review project security or after cl...
AI agents call depguard_audit_project 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 retrieves and analyzes project dependency information from package.json and lock files to produce a security audit report. It has no side effects, does not execute code, does not modify dependencies, and does not delete or overwrite data. The output is informational (a security report) used to assess risk, making it a Read operation.
From the tool's definition Tool performs scanning and auditing of dependencies to generate security reports. Key verbs: 'Scans', 'get a consolidated security report'.
Documented attack patterns abuse exactly the kind of access depguard_audit_project 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_project:
{
"version": "1",
"default": "deny",
"tools": {
"depguard_audit_project": {}
}
}depguard_audit_project 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 ALL dependencies in a project at once. Scans direct deps (full audit), transitive deps from lock file (vulnerability check), and the packageManager field. Pass the path to package.json and get a consolidated security report. Use this when the user asks to review project security or after cloning a new repo. 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_project: 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_project 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_project 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_project. 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_project 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.