clear_history

// WHEN AI AGENTS USE THIS TOOL

AI agents may call clear_history to permanently remove or destroy resources in Devtools. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON CLEAR_HISTORY

Without a policy, an AI agent could call clear_history in a loop, permanently destroying resources in Devtools. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

devtools.yaml

tools:
  clear_history:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Devtools policy for all 11 tools.

// DETAILS

Tool Name clear_history

Category Destructive

MCP Server Devtools MCP Server

Risk Level Critical

// MORE DEVTOOLS TOOLS

Destructive delete_table_row Execute run_query Write update_table_row Read get_active_queries Read get_auth_state Read get_events Read get_state Read get_table_data

View all 11 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like clear_history have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete ACR — Agent Composition Records acknowledge_signal AdButler campaign_bulk_delete_catalog_ad_items

// IN CONTEXT OF CRITICAL RISK

clear_history is one of the critical-risk operations in Devtools. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the clear_history tool do? +

Clear the event history. It is categorised as a Destructive tool in the Devtools 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_history? +

Add a rule in your Intercept YAML policy under the tools section for clear_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Devtools MCP server.

What risk level is clear_history? +

clear_history 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_history? +

Yes. Add a rate_limit block to the clear_history rule in your Intercept 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_history completely? +

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

What MCP server provides clear_history? +

clear_history is provided by the Devtools MCP server (@spooky-sync/devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.