Add a notification action to a macro. Much simpler than using km_add_action with raw XML.
AI agents use km_add_notification 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 writes a new action into an existing macro definition. A notification action displays an alert to the user; it has no destructive, financial, or code-execution implications. The modification is to a macro configuration (reversible by removing the action), so Write is the most appropriate category. Severity is low because the blast radius of adding a benign notification action is minimal.
From the tool's definition "Add a notification action to a macro" — creates/modifies a macro by appending a notification action
Documented attack patterns abuse exactly the kind of access km_add_notification 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_add_notification:
{
"version": "1",
"default": "deny",
"tools": {
"km_add_notification": {
"limits": [
{
"counter": "km_add_notification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}km_add_notification 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.
Add a notification action to a macro. Much simpler than using km_add_action with raw XML. 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_add_notification: 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_add_notification 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_add_notification 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_add_notification. 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_add_notification 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.