Get the full content of a specific conversation by ID.
AI agents call get_conversation to retrieve information from Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves conversation history from the indexed data store. It performs a lookup by ID and returns data—a classic read operation with no side effects. The blast radius is minimal: exposure would allow an agent to read past conversations (potentially sensitive, but no modification or destruction occurs). No external code execution, no financial impact, no irreversible changes.
From the tool's definition Tool name 'get_conversation' and description 'Get the full content of a specific conversation by ID' indicate retrieval of existing data without modification, deletion, or external execution.
Documented attack patterns abuse exactly the kind of access get_conversation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Brain, and nothing reaches the server without passing your rules. This is the rule we recommend for get_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"get_conversation": {}
}
}get_conversation 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 the full content of a specific conversation by ID. It is categorised as a Read tool in the Brain MCP Server, which means it retrieves data without modifying state.
Register the Brain MCP server in PolicyLayer and add a rule for get_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 Brain. Nothing to install.
get_conversation 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_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 get_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.
get_conversation is provided by the Brain MCP server (mordechaipotash/brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Brain, 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.
34 Brain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.