Medium Risk

km_add_pause

Add a pause action to a macro.

How to control km_add_pause ↓

What km_add_pause does on Keyboard Maestro

AI agents use km_add_pause to create or update resources in Keyboard Maestro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keyboard Maestro environment.

Medium Risk

Why km_add_pause needs a policy

This tool writes a new action (a pause/delay step) into an existing Keyboard Maestro macro. It modifies macro configuration data reversibly; pauses are harmless timing controls with no destructive or executable side effects on their own. Severity is low because a pause action itself cannot cause harm.

From the tool's definition 'Add a pause action to a macro' — creates/modifies a macro by inserting a pause action

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

How to control km_add_pause

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_add_pause:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "km_add_pause": {
      "limits": [
        {
          "counter": "km_add_pause_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

km_add_pause stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about km_add_pause

What does the km_add_pause tool do? +

Add a pause action to a macro. It is categorised as a Write tool in the Keyboard Maestro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on km_add_pause? +

Register the Keyboard Maestro MCP server in PolicyLayer and add a rule for km_add_pause: 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_add_pause? +

km_add_pause is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit km_add_pause? +

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

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

km_add_pause 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.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.