clear_agent_conversation

Clear agent conversation with state preservation coordination

Server Claude Code MCP - Agent Orchestration Platform nexus-digital-automations/claude_code_mcp_2
Category Destructive
Risk class Critical
Parameters 00 required

What clear_agent_conversation does on Claude Code MCP - Agent Orchestration Platform

AI agents call clear_agent_conversation to permanently remove resources in Claude Code MCP - Agent Orchestration Platform — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_agent_conversation needs a policy

Clearing a conversation permanently removes the message history. While 'state preservation coordination' implies some metadata or state may be retained, the core action (clearing the conversation) is irreversible. An AI agent misusing this could destroy valuable conversation context across multiple agent sessions, hence high severity.

From the tool's definition 'Clear agent conversation' — clearing conversation history is an irreversible deletion of the conversation state/history, despite 'state preservation coordination' suggesting some partial state may be saved

Questions about clear_agent_conversation

What does the clear_agent_conversation tool do? +

Clear agent conversation with state preservation coordination. It is categorised as a Destructive tool in the Claude Code MCP - Agent Orchestration Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_agent_conversation? +

Register the Claude Code MCP - Agent Orchestration Platform MCP server in PolicyLayer and add a rule for clear_agent_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 Claude Code MCP - Agent Orchestration Platform. Nothing to install.

What risk level is clear_agent_conversation? +

clear_agent_conversation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_agent_conversation? +

Yes. Add a rate_limit block to the clear_agent_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.

How do I block clear_agent_conversation completely? +

Set action: deny in the PolicyLayer policy for clear_agent_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.

What MCP server provides clear_agent_conversation? +

clear_agent_conversation is provided by the Claude Code MCP - Agent Orchestration Platform MCP server (nexus-digital-automations/claude_code_mcp_2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.