Deep security audit of a single npm package. Downloads the tarball, scans source code for malware, checks vulnerabilities (npm + GitHub Advisory), analyzes install scripts, verifies license. Use when you need full details on a specific package. Pass a version to audit a specific installed version...
AI agents invoke depguard_audit to trigger actions in Depguard. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool actively downloads external content (a tarball from npm), executes static analysis on it, and queries multiple external services (npm, GitHub Advisory). The act of downloading and analyzing arbitrary package content, including running checks on install scripts, constitutes an external operation with non-trivial blast radius — a misconfigured or malicious invocation could pull down malicious code or trigger…
From the tool's definition Downloads the tarball, scans source code for malware, checks vulnerabilities, analyzes install scripts
Documented attack patterns abuse exactly the kind of access depguard_audit 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:
{
"version": "1",
"default": "deny",
"tools": {
"depguard_audit": {
"limits": [
{
"counter": "depguard_audit_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}depguard_audit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Deep security audit of a single npm package. Downloads the tarball, scans source code for malware, checks vulnerabilities (npm + GitHub Advisory), analyzes install scripts, verifies license. Use when you need full details on a specific package. Pass a version to audit a specific installed version instead of latest. It is categorised as a Execute tool in the Depguard MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Depguard MCP server in PolicyLayer and add a rule for depguard_audit: 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 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the depguard_audit 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. 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 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.