Ingest a multi-turn conversation into the knowledge graph. Runs the full episodic pipeline:
AI agents use ingest_conversation to create or update resources in CodeGraph — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CodeGraph environment.
This tool writes/creates data by ingesting conversation content into the knowledge graph. It modifies the graph state by adding new nodes/edges representing the conversation, but this is a reversible write operation (data can be removed later). No code execution, deletion, or financial action is implied.
From the tool's definition Ingest a multi-turn conversation into the knowledge graph. Runs the full episodic pipeline
Documented attack patterns abuse exactly the kind of access ingest_conversation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeGraph, and nothing reaches the server without passing your rules. This is the rule we recommend for ingest_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"ingest_conversation": {
"limits": [
{
"counter": "ingest_conversation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ingest_conversation 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.
Ingest a multi-turn conversation into the knowledge graph. Runs the full episodic pipeline:. It is categorised as a Write tool in the CodeGraph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CodeGraph MCP server in PolicyLayer and add a rule for ingest_conversation: 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 CodeGraph. Nothing to install.
ingest_conversation 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 ingest_conversation 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 ingest_conversation. 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.
ingest_conversation is provided by the CodeGraph MCP server (phoenixrr2113/codebase-graph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeGraph, 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.
18 CodeGraph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.