ALWAYS use this tool when asked about request lifecycles, execution paths, or how data flows through the system. Traces execution flows from entry points (routes, event listeners, queue consumers) through the call graph. Shows call chain depth, per-step file location, and terminal operations (DB ...
AI agents call nm_flows 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 retrieves and visualizes information about code execution paths and data flows from the Neo4j knowledge graph. It performs static analysis of the codebase to trace call chains and identify terminal operations, but does not execute code, modify data, delete resources, or perform any side effects.
From the tool's definition The tool 'traces execution flows from entry points through the call graph' and 'shows call chain depth, per-step file location, and terminal operations'.
Documented attack patterns abuse exactly the kind of access nm_flows 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_flows:
{
"version": "1",
"default": "deny",
"tools": {
"nm_flows": {}
}
}nm_flows 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 request lifecycles, execution paths, or how data flows through the system. Traces execution flows from entry points (routes, event listeners, queue consumers) through the call graph. Shows call chain depth, per-step file location, and terminal operations (DB writes, API calls). 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_flows: 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_flows 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_flows 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_flows. 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_flows 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.