Critical Risk →

clear_checked

Remove all checked (completed) items from a list

Part of the Lystbot server.

clear_checked can permanently delete data in Lystbot, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LYSTBOT →

Free to start. No card required.

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

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_checked"
  ]
}

See the full Lystbot policy for all 22 tools.

Get this rule live on your own Lystbot server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LYSTBOT →

View all 22 tools →

These attack patterns abuse exactly the kind of access clear_checked gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so clear_checked only ever does what you allow.

SECURE LYSTBOT →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the clear_checked tool do? +

Remove all checked (completed) items from a list. It is categorised as a Destructive tool in the Lystbot 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_checked? +

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

What risk level is clear_checked? +

clear_checked 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_checked? +

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

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

clear_checked is provided by the Lystbot MCP server (lystbot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lystbot tool call.

Deterministic rules across all 22 Lystbot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.