// SCAN REPORT

NOMIK

21 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
21 read-only
21 tools total

Community server · catalogue entry verified 11/06/2026

How to control NOMIK ↓

TOOL MAP

What NOMIK exposes to your agents

Read (21) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

✕

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control NOMIK

PolicyLayer is an MCP gateway — it sits between your AI agents and NOMIK, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations
{
  "nm_audit": {
    "limits": [
      {
        "counter": "nm_audit_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register NOMIK — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON NOMIK →

Free to start. No card required.

FULL CATALOGUE

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 results. Read nm_changes ALWAYS use this tool when asked what changed recently, today, or this week. Returns nodes that were modified s Read nm_communities ALWAYS use this tool when asked about code organization, modules, coupling, or architecture structure. Detects Read nm_context ALWAYS use this tool when asked about a specific file or function context — what it contains, calls, is called Read nm_diff ALWAYS use this tool when asked about architecture drift, what changed between two scans, or comparing codebas Read nm_explain ALWAYS use this tool when asked to explain what a function/class does, how it connects to other code, or who c Read nm_flows ALWAYS use this tool when asked about request lifecycles, execution paths, or how data flows through the syste Read nm_guard ALWAYS use this tool when asked about code quality gates, CI checks, or whether the codebase passes quality th Read nm_health ALWAYS use this tool when asked about codebase health, code quality, dead code, god files, duplicates, or infr 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: sta Read nm_path ALWAYS use this tool when asked to find the path or connection between two code entities. Returns detailed ste Read nm_projects ALWAYS use this tool when asked about available projects or which codebases are tracked. Lists all projects in Read nm_rules ALWAYS use this tool when asked about architecture rules, code quality policies, or whether the codebase follo 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 co Read nm_test_impact ALWAYS use this tool when asked which tests to run, which tests are affected by a change, or test coverage imp Read nm_trace ALWAYS use this tool when asked how two symbols are connected or to trace the dependency chain between them. R Read nm_db_impact ALWAYS use this tool when asked about database tables, who reads/writes a table, or column-level impact. Retur Read nm_rename ALWAYS use this tool when asked about renaming a symbol or understanding the impact of renaming. Returns the s Read nm_wiki ALWAYS use this tool when asked to generate, write, or create documentation for a module, package, or codebase
EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Sperax Ecosystem Crypto & DeFI MCP Server 1318 tools
automation
Mcp Afip 1300 tools
automation
Mcp Ap2 1300 tools
automation
BNB Chain MCP 1240 tools
automation
Nodebench 824 tools
automation
Amazon Bedrock Knowledge Base Retrieval MCP Server 805 tools
automation
Amazon Data Processing MCP Server 805 tools
automation
Amazon ECS MCP Server 805 tools
automation
FAQ

Questions about NOMIK

Is the NOMIK MCP server safe to use without restrictions? +

The NOMIK server is primarily read-only with 21 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the NOMIK MCP server expose? +

21 tools across 3 categories: Execute, Read, Write. 21 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on NOMIK? +

Register the NOMIK MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every NOMIK tool call.

Deterministic rules across all 21 NOMIK tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NOMIK →

Free to start. No card required.

21 NOMIK tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.