clear_edit_context

Clear all persistent edit-context references without adding an Undo history entry.

SERVERCutpilot SOURCEHellotravisss/cutpilot

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cutpilot/clear-edit-context.md

WHAT IT DOES

What clear_edit_context does on Cutpilot

AI agents call clear_edit_context to permanently remove resources in Cutpilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear_edit_context is rated Critical

An AI agent that decides to call clear_edit_context doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Cutpilot is gone. There is no undo for destructive operations.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_edit_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_edit_context, this is the rule to start with:

clear_edit_context Hidden

clear_edit_context is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_edit_context"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cutpilot, apply this rule, and every clear_edit_context call is checked against it from then on.

FAQ

Questions about clear_edit_context

What does the clear_edit_context tool do? +

Clear all persistent edit-context references without adding an Undo history entry. It is categorised as a Destructive tool in the Cutpilot 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_edit_context? +

Register the Cutpilot MCP server in PolicyLayer and add a rule for clear_edit_context: 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 Cutpilot. Nothing to install.

What risk level is clear_edit_context? +

clear_edit_context 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_edit_context? +

Yes. Add a rate_limit block to the clear_edit_context 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_edit_context completely? +

Set action: deny in the PolicyLayer policy for clear_edit_context. 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_edit_context? +

clear_edit_context is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cutpilot, and thousands of servers like it.

This server

All 219 Cutpilot tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →