Get the XML definition of a specific action in a macro. Actions are 1-indexed.
AI agents call km_get_action_xml to retrieve information from Keyboard Maestro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves the XML representation of an existing action within a Keyboard Maestro macro. This is a read-only operation with no side effects, no code execution, and no data modification. The sibling tools like km_add_* and km_add_execute_macro suggest this server can perform Execute operations, but this specific tool is purely retrieving information.
From the tool's definition Tool name contains 'get' and description states 'Get the XML definition of a specific action in a macro' — retrieves data without modification or execution.
Documented attack patterns abuse exactly the kind of access km_get_action_xml 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_get_action_xml:
{
"version": "1",
"default": "deny",
"tools": {
"km_get_action_xml": {}
}
} km_get_action_xml is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the XML definition of a specific action in a macro. Actions are 1-indexed. It is categorised as a Read tool in the Keyboard Maestro MCP Server, which means it retrieves data without modifying state.
Register the Keyboard Maestro MCP server in PolicyLayer and add a rule for km_get_action_xml: 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_get_action_xml is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the km_get_action_xml 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_get_action_xml. 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_get_action_xml 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.