ALWAYS use this tool when asked which tests to run, which tests are affected by a change, or test coverage impact. Traces the knowledge graph from a changed symbol or file to find all test files that should be re-run. Do NOT manually search for test files — this tool has the complete dependency p...
AI agents call nm_test_impact 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 reads from the Neo4j knowledge graph to analyze test dependencies and impact. It has no side effects, does not execute tests, does not modify data, and does not delete anything. It is purely informational retrieval used for impact analysis planning. The severity is low because misuse would only provide incorrect test recommendations without directly affecting systems.
From the tool's definition Tool 'traces the knowledge graph from a changed symbol or file to find all test files that should be re-run' — it queries and retrieves test dependency information without modifying, deleting, or executing anything.
Documented attack patterns abuse exactly the kind of access nm_test_impact 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_test_impact:
{
"version": "1",
"default": "deny",
"tools": {
"nm_test_impact": {}
}
}nm_test_impact 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 which tests to run, which tests are affected by a change, or test coverage impact. Traces the knowledge graph from a changed symbol or file to find all test files that should be re-run. Do NOT manually search for test files — this tool has the complete dependency picture. 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_test_impact: 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_test_impact 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_test_impact 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_test_impact. 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_test_impact 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.