km_get_log

THE RISK

Low Risk

Why km_get_log needs a policy

The tool retrieves and queries existing log data from Keyboard Maestro Engine. The verb 'Get' combined with 'log entries' and optional filters describes a read-only operation that does not create, modify, delete, or execute any actions. Log retrieval has minimal blast radius—it only exposes historical information without side effects or operational impact.

From the tool's definition Tool name 'km_get_log' and description 'Get raw log entries from Keyboard Maestro Engine log with optional filters' indicate data retrieval with no modification capability.

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

POLICY

How to control km_get_log

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "km_get_log": {}
  }
}

km_get_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Keyboard Maestro tools

Destructive km_delete_action Delete a specific action from a macro. Actions are 1-indexed. WARNING: This cannot be undo 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 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 km_search_replace_action Search and replace text within a specific action in a macro. Useful for fixing typos or up

All 34 Keyboard Maestro tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about km_get_log

What does the km_get_log tool do? +

Get raw log entries from Keyboard Maestro Engine log with optional filters. It is categorised as a Read tool in the Keyboard Maestro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on km_get_log? +

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

km_get_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit km_get_log? +

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

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

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

CHECK YOUR STACK →