light_delete_rule

Delete one on-device lighting rule by id.

SERVERTolpo SOURCEsignerless/tolpo

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/tolpo/light-delete-rule.md

WHAT IT DOES

What light_delete_rule does on Tolpo

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

RISK

Why light_delete_rule is rated Critical

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs light_delete_rule safely

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

light_delete_rule Hidden

light_delete_rule 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": [
    "light_delete_rule"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about light_delete_rule

What does the light_delete_rule tool do? +

Delete one on-device lighting rule by id. It is categorised as a Destructive tool in the Tolpo 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 light_delete_rule? +

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

What risk level is light_delete_rule? +

light_delete_rule 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 light_delete_rule? +

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

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

light_delete_rule is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tolpo, and thousands of servers like it.

This server

All 243 Tolpo tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →