Parse a single source file and add its entities to the graph
AI agents use add_file to create or update resources in CodeRAG — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CodeRAG environment.
This tool creates new entities in the graph representation of a codebase. While reversible (entities can be deleted via 'delete_node' and 'delete_edge'), it modifies the knowledge base state. The impact is moderate because malicious misuse could pollute the graph with incorrect code relationships, affecting AI reasoning about the codebase, but it doesn't execute code, destroy data permanently, or move funds.
From the tool's definition Tool name 'add_file' combined with description 'add its entities to the graph' indicates the tool creates or modifies data by inserting file parsing results into the Neo4J knowledge graph.
Documented attack patterns abuse exactly the kind of access add_file 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 add_file:
{
"version": "1",
"default": "deny",
"tools": {
"add_file": {
"limits": [
{
"counter": "add_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Parse a single source file and add its entities to the graph. It is categorised as a Write tool in the CodeRAG MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CodeRAG MCP server in PolicyLayer and add a rule for add_file: 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.
add_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_file 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 add_file. 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.
add_file 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.