ALWAYS use this tool when asked to generate, write, or create documentation for a module, package, or codebase. Returns structured data: file index with function counts, top functions ranked by caller count, health report (dead code, god files, duplicates), and cross-service links. Do NOT manuall...
AI agents call nm_wiki 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.
The tool queries and retrieves data from the knowledge graph to support documentation generation. It does not write, execute, or modify anything — it returns structured read-only data about the codebase. The instruction 'call this tool first to get the authoritative data' confirms it is a data retrieval step before any output is formatted externally.
From the tool's definition Returns structured data: file index with function counts, top functions ranked by caller count, health report...from the knowledge graph
Documented attack patterns abuse exactly the kind of access nm_wiki 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_wiki:
{
"version": "1",
"default": "deny",
"tools": {
"nm_wiki": {}
}
}nm_wiki 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 generate, write, or create documentation for a module, package, or codebase. Returns structured data: file index with function counts, top functions ranked by caller count, health report (dead code, god files, duplicates), and cross-service links. Do NOT manually read source files to write docs — call this tool first to get the authoritative data from the knowledge graph, then format the output. 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_wiki: 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_wiki 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_wiki 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_wiki. 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_wiki 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.