// SCAN REPORT

Keyboard Maestro

34 tools. 25 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

25 can modify or destroy data

9 read-only

34 tools total

Community server · catalogue entry verified 11/06/2026

How to control Keyboard Maestro ↓

TOOL MAP

What Keyboard Maestro exposes to your agents

Read (9) Write / Execute (21) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Keyboard Maestro tools

Destructive · High km_delete_action This tool permanently removes data (macro actions) from stored macros without possibility of recovery. Destructive · High km_delete_macro This tool permanently removes macros without recovery options. Destructive · High km_delete_trigger Deleting a trigger is an irreversible data modification that removes functional configuration from a macro. Destructive · High km_manage_group The tool supports deletion of macro groups, which is irreversible.

25 of Keyboard Maestro's 34 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Keyboard Maestro

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

Deny destructive operations

{
  "km_delete_action": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "km_search_replace_action": {
    "limits": [
      {
        "counter": "km_search_replace_action_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "km_get_action_xml": {
    "limits": [
      {
        "counter": "km_get_action_xml_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Keyboard Maestro — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON KEYBOARD MAESTRO →

Free to start. No card required.

FULL CATALOGUE

All 34 Keyboard Maestro tools

DESTRUCTIVE 4 tools

Destructive km_delete_action Delete a specific action from a macro. Actions are 1-indexed. WARNING: This cannot be undone! Destructive km_delete_macro Delete a macro by name or UID. WARNING: This cannot be undone! Destructive km_delete_trigger Delete a trigger from a macro. Triggers are 1-indexed. Destructive km_manage_group Manage macro groups (create, delete, toggle, list).

EXECUTE 3 tools

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 18 tools

Write km_search_replace_action Search and replace text within a specific action in a macro. Useful for fixing typos or updating values. Write km_add_action Add an action to an existing macro using XML. Write km_add_calculation Add an action to set a variable to the result of a calculation (e.g., Write km_add_display_text Add an action to display text in a window. Write km_add_if_calculation Add an If-Then-Else action that checks a calculation condition (e.g., Write km_add_if_variable_contains Add an If-Then-Else action that checks if a variable contains a value. Write km_add_notification Add a notification action to a macro. Much simpler than using km_add_action with raw XML. Write km_add_pause Add a pause action to a macro. Write km_add_set_variable Add an action to set a variable to a text value. Write km_add_trigger Add a trigger to a macro using XML. Write km_clone_macro Duplicate an existing macro. Optionally provide a new name. Write km_create_macro Create a new macro with a name. Optionally include action XML to add an initial action. Write km_enable_macro Enable or disable a macro. Write km_manage_variable Manage Keyboard Maestro variables (get, set, delete). Write km_move_action Move an action to a new position index. Subsequent actions will shift down. Write km_move_macro Move a macro to a different macro group. Write km_set_action_xml Set/replace the XML of a specific action in a macro. Use km_get_action_xml first to get the current XML. Write km_set_trigger_xml Set/replace the XML of a specific trigger in a macro. Use km_get_trigger_xml first to understand the format.

READ 9 tools

Read km_get_action_xml Get the XML definition of a specific action in a macro. Actions are 1-indexed. Read km_get_errors Get recent errors and failures from Keyboard Maestro Engine log. Returns errors grouped by macro with timestam Read km_get_log Get raw log entries from Keyboard Maestro Engine log with optional filters. Read km_get_macro Get details about a specific macro by name or UID. Read km_get_macro_xml Get the full XML definition of a macro. Useful for understanding macro structure or creating similar macros. Read km_get_trigger_xml Get the XML definition of a specific trigger in a macro. Triggers are 1-indexed. Read km_list_actions List all actions in a macro with their index, name, and enabled status. Read km_list_macros List all macros in Keyboard Maestro with their names and UIDs. Read km_search_macros Search for macros by name (case-insensitive partial match). returns name and UID.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Keyboard Maestro

Can an AI agent delete data through the Keyboard Maestro MCP server? +

Yes. The Keyboard Maestro server exposes 4 destructive tools including km_delete_action, km_delete_macro, km_delete_trigger. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Keyboard Maestro? +

The Keyboard Maestro server has 18 write tools including km_search_replace_action, km_add_action, km_add_calculation. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Keyboard Maestro.

How many tools does the Keyboard Maestro MCP server expose? +

34 tools across 4 categories: Destructive, Execute, Read, Write. 9 are read-only. 25 can modify, create, or delete data.

How do I enforce a policy on Keyboard Maestro? +

Register the Keyboard Maestro MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Keyboard Maestro tool call.

Deterministic rules across all 34 Keyboard Maestro tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON KEYBOARD MAESTRO →

Free to start. No card required.

34 Keyboard Maestro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.