When you need functionality (e.g.
AI agents call depguard_should_use 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.
The description is incomplete and provides no meaningful information about what the tool does. Based on the name 'depguard_should_use' and its context among security audit/analysis tools, it likely performs a read/query operation to advise whether a dependency should be used, but this cannot be confirmed. Lowering confidence significantly due to the uninformative description.
From the tool's definition Tool description is truncated/uninformative: 'When you need functionality (e.g.' — no actionable content visible
Documented attack patterns abuse exactly the kind of access depguard_should_use 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_should_use:
{
"version": "1",
"default": "deny",
"tools": {
"depguard_should_use": {}
}
} depguard_should_use 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.
When you need functionality (e.g. 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_should_use: 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_should_use 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_should_use 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_should_use. 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_should_use 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.