// MCP TOOL REFERENCE

NOMIK TOOLS

21 tools from the NOMIK MCP Server, categorised by risk level.

View the NOMIK policy →
// ALL 21 NOMIK TOOLS
READ 21 tools
Read nm_audit ALWAYS use this tool when asked about dependency vulnerabilities, security audits, or npm/pnpm audit result... Read nm_changes ALWAYS use this tool when asked what changed recently, today, or this week. Returns nodes that were modifie... Read nm_communities ALWAYS use this tool when asked about code organization, modules, coupling, or architecture structure. Dete... Read nm_context ALWAYS use this tool when asked about a specific file or function context — what it contains, calls, is cal... Read nm_diff ALWAYS use this tool when asked about architecture drift, what changed between two scans, or comparing code... Read nm_explain ALWAYS use this tool when asked to explain what a function/class does, how it connects to other code, or wh... Read nm_flows ALWAYS use this tool when asked about request lifecycles, execution paths, or how data flows through the sy... Read nm_guard ALWAYS use this tool when asked about code quality gates, CI checks, or whether the codebase passes quality... Read nm_health ALWAYS use this tool when asked about codebase health, code quality, dead code, god files, duplicates, or i... Read nm_impact ALWAYS use this tool when asked Read nm_onboard ALWAYS use this tool when asked to describe, summarize, or understand a codebase. Returns a full briefing: ... Read nm_path ALWAYS use this tool when asked to find the path or connection between two code entities. Returns detailed ... Read nm_projects ALWAYS use this tool when asked about available projects or which codebases are tracked. Lists all projects... Read nm_rules ALWAYS use this tool when asked about architecture rules, code quality policies, or whether the codebase fo... Read nm_search ALWAYS use this tool when the user mentions Read nm_service_links ALWAYS use this tool when asked about cross-service dependencies, microservice connections, or how services... Read nm_test_impact ALWAYS use this tool when asked which tests to run, which tests are affected by a change, or test coverage ... Read nm_trace ALWAYS use this tool when asked how two symbols are connected or to trace the dependency chain between them... Read nm_db_impact ALWAYS use this tool when asked about database tables, who reads/writes a table, or column-level impact. Re... Read nm_rename ALWAYS use this tool when asked about renaming a symbol or understanding the impact of renaming. Returns th... Read nm_wiki ALWAYS use this tool when asked to generate, write, or create documentation for a module, package, or codeb...

Route NOMIK through PolicyLayer and every one of its 21 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the NOMIK MCP server have? +

The NOMIK MCP server exposes 21 tools across 1 categories: Read.

How do I enforce policies on NOMIK tools? +

Route the NOMIK server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do NOMIK tools fall into? +

NOMIK tools are categorised as Read (21). Each category has a recommended default policy.

Enforce policy on every NOMIK tool call.

Start from NOMIK, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.