ALWAYS use this tool when asked about dependency vulnerabilities, security audits, or npm/pnpm audit results. Checks for vulnerable packages and cross-references with the knowledge graph to show which files import them (blast radius). Do NOT run npm audit manually — this tool integrates results w...
AI agents call nm_audit to retrieve information from NOMIK without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes dependency vulnerability data, querying the knowledge graph to identify which files import vulnerable packages. It is purely a read/query operation — it retrieves audit results and maps them to the codebase graph. No data is modified, deleted, or executed.
From the tool's definition Checks for vulnerable packages and cross-references with the knowledge graph to show which files import them (blast radius)
Documented attack patterns abuse exactly the kind of access nm_audit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NOMIK, and nothing reaches the server without passing your rules. This is the rule we recommend for nm_audit:
{
"version": "1",
"default": "deny",
"tools": {
"nm_audit": {}
}
}nm_audit 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.
ALWAYS use this tool when asked about dependency vulnerabilities, security audits, or npm/pnpm audit results. Checks for vulnerable packages and cross-references with the knowledge graph to show which files import them (blast radius). Do NOT run npm audit manually — this tool integrates results with the graph. It is categorised as a Read tool in the NOMIK MCP Server, which means it retrieves data without modifying state.
Register the NOMIK MCP server in PolicyLayer and add a rule for nm_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 NOMIK. Nothing to install.
nm_audit 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 nm_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 nm_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.
nm_audit is provided by the NOMIK MCP server (willfreed1/nomik). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NOMIK, 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.
21 NOMIK tools catalogued and risk-classified — across an index of 43,000+ MCP servers.