get_conversation_trace
A read tool on the 23 Open Chat Reviewer MCP server.
This record as markdown: /tools/23-open-chat-reviewer/get-conversation-trace.md
What get_conversation_trace does on 23 Open Chat Reviewer
AI agents call get_conversation_trace to retrieve information from 23 Open Chat Reviewer without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_conversation_trace is rated Low
Even though get_conversation_trace only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_conversation_trace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 23 Open Chat Reviewer, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_conversation_trace, this is the rule to start with:
get_conversation_trace is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 23 Open Chat Reviewer, apply this rule, and every get_conversation_trace call is checked against it from then on.
Questions about get_conversation_trace
get_conversation_trace is a read tool on the 23 Open Chat Reviewer MCP server. It is categorised as a Read tool in the 23 Open Chat Reviewer MCP Server, which means it retrieves data without modifying state.
Register the 23 Open Chat Reviewer MCP server in PolicyLayer and add a rule for get_conversation_trace: 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 23 Open Chat Reviewer. Nothing to install.
get_conversation_trace 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_trace 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_trace. 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_trace is provided by the 23 Open Chat Reviewer MCP server (MiddleDistances/23-open-chat-reviewer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 23 Open Chat Reviewer, and thousands of servers like it.
This server
Across the catalogue