Audit an npm package
AI agents call audit_supply_chain to retrieve information from Mcp Shield without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Auditing an npm package is a read-only operation that retrieves metadata, vulnerability data, dependency information, and other package attributes for analysis purposes. It performs no modifications, deletions, code execution, or financial transactions. The tool's purpose within mcp-shield (security auditing) further confirms it is informational and non-mutating.
From the tool's definition Tool name is 'audit_supply_chain' and description states 'Audit an npm package' — auditing is an inspection/analysis activity that queries and retrieves information about a package without modifying it.
Attacks that exploit this kind of access
Audit an npm package. It is categorised as a Read tool in the Mcp Shield MCP Server, which means it retrieves data without modifying state.
Register the Mcp Shield MCP server in PolicyLayer and add a rule for audit_supply_chain: 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 Mcp Shield. Nothing to install.
audit_supply_chain 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 audit_supply_chain 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 audit_supply_chain. 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.
audit_supply_chain is provided by the Mcp Shield MCP server (muhannad-hash/mcp-shield). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →