Create a new macro with a name. Optionally include action XML to add an initial action.
AI agents use km_create_macro 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.
This tool creates a new Keyboard Maestro macro, which is a Write operation. However, the severity is high because macros can contain arbitrary actions including shell scripts, file operations, and system commands. Once created, these macros can be triggered and executed, making the blast radius significant if an AI agent creates a malicious or unintended macro.
From the tool's definition "Create a new macro with a name. Optionally include action XML to add an initial action."
Documented attack patterns abuse exactly the kind of access km_create_macro gives an agent:
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_create_macro:
{
"version": "1",
"default": "deny",
"tools": {
"km_create_macro": {
"limits": [
{
"counter": "km_create_macro_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}km_create_macro 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.
Free to start. No card required.
Create a new macro with a name. Optionally include action XML to add an initial action. 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.
Register the Keyboard Maestro MCP server in PolicyLayer and add a rule for km_create_macro: 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.
km_create_macro is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the km_create_macro 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.
Set action: deny in the PolicyLayer policy for km_create_macro. 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.
km_create_macro 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.
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.