km_delete_trigger

THE RISK

Critical Risk

Why km_delete_trigger needs a policy

Deleting a trigger is an irreversible data modification that removes functional configuration from a macro. While it doesn't destroy the macro itself, it permanently removes trigger associations that activate the macro. This fits the Destructive category (irreversibly deletes or overwrites data, or actions that cannot be undone).

From the tool's definition Tool name contains 'delete' and description states 'Delete a trigger from a macro'. The action is irreversible—once a trigger is removed, it cannot be automatically recovered without external backup or undo mechanisms outside this tool's scope.

Documented attack patterns abuse exactly the kind of access km_delete_trigger gives an agent:

POLICY

How to control km_delete_trigger

PolicyLayer is an MCP gateway — it sits between your AI agents and Keyboard Maestro, and nothing reaches the server without passing your rules. This is the rule we recommend for km_delete_trigger:

policy.json

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

km_delete_trigger disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Keyboard Maestro — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Keyboard Maestro tools

Destructive km_delete_action Delete a specific action from a macro. Actions are 1-indexed. WARNING: This cannot be undo Destructive km_delete_macro Delete a macro by name or UID. WARNING: This cannot be undone! Destructive km_manage_group Manage macro groups (create, delete, toggle, list). Execute km_run_macro Execute a macro by name or UID. Execute km_add_execute_macro Add an action to execute another macro. Execute km_add_shell_script Add an action to execute a shell script. Write km_search_replace_action Search and replace text within a specific action in a macro. Useful for fixing typos or up Write km_add_action Add an action to an existing macro using XML.

All 34 Keyboard Maestro tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Keyboard Maestro → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about km_delete_trigger

What does the km_delete_trigger tool do? +

Delete a trigger from a macro. Triggers are 1-indexed. It is categorised as a Destructive tool in the Keyboard Maestro 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 km_delete_trigger? +

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

What risk level is km_delete_trigger? +

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

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

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

km_delete_trigger is provided by the Keyboard Maestro MCP server (saihgupr/keyboard-maestro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Keyboard Maestro tool call.

Start from Keyboard Maestro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →