Audit multiple packages in one call. Accepts an array of names or a dependencies object from package.json. Use depguard_audit_project instead if you have a package.json path.
AI agents call depguard_audit_bulk 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 performs security auditing/querying of packages for vulnerabilities. It reads and analyzes package information without modifying any data, executing code, or performing destructive actions. It is a read/query operation that returns audit results.
From the tool's definition Audit multiple packages in one call. Accepts an array of names or a dependencies object from package.json.
Documented attack patterns abuse exactly the kind of access depguard_audit_bulk 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_bulk:
{
"version": "1",
"default": "deny",
"tools": {
"depguard_audit_bulk": {}
}
}depguard_audit_bulk 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 multiple packages in one call. Accepts an array of names or a dependencies object from package.json. Use depguard_audit_project instead if you have a package.json path. 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_bulk: 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_bulk 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_bulk 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_bulk. 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_bulk 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.