AI agents call get_edge 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 existing data from the graph without modifying, deleting, or executing operations. It follows the 'get' pattern typical of Read operations. The low severity reflects that querying a knowledge graph poses minimal risk—no data is altered, deleted, or executed.
From the tool's definition Tool name 'get_edge' and description 'Get an edge by ID' indicate a retrieval operation with no side effects. Edges in a Neo4J knowledge graph represent relationships between code entities; fetching an edge is a query operation.
Documented attack patterns abuse exactly the kind of access get_edge 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_edge:
{
"version": "1",
"default": "deny",
"tools": {
"get_edge": {}
}
}get_edge 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 an edge 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_edge: 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_edge 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_edge 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_edge. 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_edge 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.