This record as markdown: /tools/openclaw/conversation-get.md
What conversation_get does on OpenClaw
AI agents call conversation_get to retrieve information from OpenClaw without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why conversation_get is rated Low
This tool retrieves a single conversation record by its session key identifier. The verb 'Get' and the absence of any language suggesting modification, deletion, or execution means this is a read-only query operation. The severity is low because retrieving conversation history has minimal blast radius—it does not modify data, execute code, or trigger external side effects.
From the tool's definition Tool name 'conversation_get' and description 'Get one OpenClaw conversation by session key' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs conversation_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For conversation_get, this is the rule to start with:
conversation_get 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 OpenClaw, apply this rule, and every conversation_get call is checked against it from then on.
Questions about conversation_get
Get one OpenClaw conversation by session key. It is categorised as a Read tool in the OpenClaw MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP server in PolicyLayer and add a rule for conversation_get: 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 OpenClaw. Nothing to install.
conversation_get 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 conversation_get 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 conversation_get. 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.
conversation_get is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue