ALWAYS use this tool when asked about code quality gates, CI checks, or whether the codebase passes quality thresholds. Returns dead code count, god file count, duplicate count, and whether each passes the given threshold. Use this instead of manually counting issues.
AI agents call nm_guard 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_guard queries a code intelligence graph to fetch quality gate status and metric counts. It performs no mutations, executions, deletions, or financial operations. The function is purely informational—gathering existing analysis results about code quality thresholds. This is a safe Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool 'returns dead code count, god file count, duplicate count' — it retrieves and reports pre-computed code quality metrics without modifying data, executing external operations, or triggering side effects.
Documented attack patterns abuse exactly the kind of access nm_guard 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_guard:
{
"version": "1",
"default": "deny",
"tools": {
"nm_guard": {}
}
}nm_guard 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 code quality gates, CI checks, or whether the codebase passes quality thresholds. Returns dead code count, god file count, duplicate count, and whether each passes the given threshold. Use this instead of manually counting issues. 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_guard: 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_guard 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_guard 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_guard. 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_guard 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.