ALWAYS use this tool when asked about renaming a symbol or understanding the impact of renaming. Returns the symbol definition, all callers, importers, and affected files — everything needed to safely rename across the codebase. Do NOT manually grep for references — this tool uses the knowledge g...
AI agents call nm_rename 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.
Despite being named 'nm_rename', the tool description explicitly states it only *returns* information (symbol definition, callers, importers, affected files) needed to understand the impact of a rename. It performs analysis via the knowledge graph rather than actually executing any renaming operation. This is a read/query tool for impact analysis, not a write tool that modifies code.
From the tool's definition Returns the symbol definition, all callers, importers, and affected files — everything needed to safely rename across the codebase
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access nm_rename 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_rename:
{
"version": "1",
"default": "deny",
"tools": {
"nm_rename": {}
}
}nm_rename 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 renaming a symbol or understanding the impact of renaming. Returns the symbol definition, all callers, importers, and affected files — everything needed to safely rename across the codebase. Do NOT manually grep for references — this tool uses the knowledge graph for accurate results. 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_rename: 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_rename 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_rename 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_rename. 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_rename 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.