get_conversation_history
AI agents call get_conversation_history to retrieve information from Cluster Execution MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves conversation history—a read-only query operation with no side effects. No data is created, modified, executed, or deleted. Even though the description is absent, the naming convention and context of a cluster execution server strongly indicate this is a data retrieval function.
From the tool's definition Tool name 'get_conversation_history' indicates data retrieval. Description is empty, limiting confidence. Sibling tools on the server (check_for_new_messages, cluster_status, etc.) suggest this server primarily supports querying and command execution; a…
Attacks that exploit this kind of access
get_conversation_history. It is categorised as a Read tool in the Cluster Execution MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cluster Execution MCP Server MCP server in PolicyLayer and add a rule for get_conversation_history: 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 Cluster Execution MCP Server. Nothing to install.
get_conversation_history 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_history 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_history. 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_history is provided by the Cluster Execution MCP Server MCP server (marc-shade/cluster-execution-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →