ALWAYS use this tool when asked how two symbols are connected or to trace the dependency chain between them. Returns the shortest path through the knowledge graph. Do NOT manually inspect files to understand connections.
AI agents call nm_trace 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.
nm_trace queries a Neo4j knowledge graph to retrieve dependency chain information between symbols. This is a read-only operation that retrieves and returns data without modification, creation, deletion, or side effects. The tool does not execute code, modify the graph, or trigger external operations—it solely navigates and returns existing graph data.
From the tool's definition Tool returns the shortest path through a knowledge graph; the description explicitly states it 'Returns the shortest path through the knowledge graph' and instructs users to use it instead of manual file inspection.
Documented attack patterns abuse exactly the kind of access nm_trace 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_trace:
{
"version": "1",
"default": "deny",
"tools": {
"nm_trace": {}
}
}nm_trace 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 how two symbols are connected or to trace the dependency chain between them. Returns the shortest path through the knowledge graph. Do NOT manually inspect files to understand connections. 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_trace: 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_trace 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_trace 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_trace. 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_trace 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.