ALWAYS use this tool when asked to find the path or connection between two code entities. Returns detailed steps with node types and relationship types. More detailed than nm_trace — shows each step in the path.
AI agents call nm_path 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_path queries and traverses the Neo4j knowledge graph to find connections between code entities, returning path information. This is a read-only operation that retrieves existing data about code structure and relationships without creating, modifying, deleting, or executing anything. The tool has no side effects and poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Returns detailed steps with node types and relationship types' and 'shows each step in the path' — purely informational retrieval operations on the knowledge graph with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access nm_path 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_path:
{
"version": "1",
"default": "deny",
"tools": {
"nm_path": {}
}
}nm_path 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 to find the path or connection between two code entities. Returns detailed steps with node types and relationship types. More detailed than nm_trace — shows each step in the path. 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_path: 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_path 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_path 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_path. 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_path 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.