ALWAYS use this tool when asked about cross-service dependencies, microservice connections, or how services communicate. Returns producer/consumer pairs for message queues, event buses, and API calls across service boundaries.
AI agents call nm_service_links 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 a Neo4j knowledge graph to retrieve cross-service dependency information. It has no side effects: it does not create, modify, delete, or execute code/commands. The action is read-only analysis of service architecture. Given the context that NOMIK builds a persistent knowledge graph and exposes it to AI assistants, this tool fits the 'Read' category for safe data retrieval.
From the tool's definition Tool description states it 'Returns producer/consumer pairs' and 'how services communicate' — purely informational retrieval of dependency and messaging topology. No modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access nm_service_links 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_service_links:
{
"version": "1",
"default": "deny",
"tools": {
"nm_service_links": {}
}
}nm_service_links 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 cross-service dependencies, microservice connections, or how services communicate. Returns producer/consumer pairs for message queues, event buses, and API calls across service boundaries. 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_service_links: 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_service_links 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_service_links 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_service_links. 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_service_links 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.