ALWAYS use this tool when asked what changed recently, today, or this week. Returns nodes that were modified since a given date with their types and file paths.
AI agents call nm_changes 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 queries historical metadata about code changes (nodes modified since a date) and presents the results. It performs read-only operations on the codebase graph without creating, modifying, deleting, executing, or committing any changes. The blast radius of misuse is minimal — an AI agent could only retrieve unwanted change history, not cause harm.
From the tool's definition Tool description states it 'Returns nodes that were modified since a given date' — a pure retrieval operation with no side effects. The verb 'Returns' indicates querying/fetching data from the Neo4j knowledge graph.
Documented attack patterns abuse exactly the kind of access nm_changes 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_changes:
{
"version": "1",
"default": "deny",
"tools": {
"nm_changes": {}
}
}nm_changes 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 what changed recently, today, or this week. Returns nodes that were modified since a given date with their types and file paths. 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_changes: 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_changes 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_changes 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_changes. 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_changes 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.