AI agents call get_node to retrieve information from CodeRAG without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single code node from the Neo4j knowledge graph by its identifier. It is a read-only query that returns data without side effects, matching the 'Read' category definition. The low severity reflects that retrieving code structure information poses minimal risk even if misused by an agent, as no data is created, modified, or deleted.
From the tool's definition Tool name is 'get_node' and description states 'Get a code node by ID' — a retrieval operation with no modification or deletion.
Documented attack patterns abuse exactly the kind of access get_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeRAG, and nothing reaches the server without passing your rules. This is the rule we recommend for get_node:
{
"version": "1",
"default": "deny",
"tools": {
"get_node": {}
}
}get_node 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.
Get a code node by ID. It is categorised as a Read tool in the CodeRAG MCP Server, which means it retrieves data without modifying state.
Register the CodeRAG MCP server in PolicyLayer and add a rule for get_node: 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 CodeRAG. Nothing to install.
get_node 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 get_node 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 get_node. 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.
get_node is provided by the CodeRAG MCP server (jonnoc/coderag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeRAG, 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.
38 CodeRAG tools catalogued and risk-classified — across an index of 43,000+ MCP servers.