execute_app_command · Iac MCP: Risk & Policy

WHAT IT DOES

What execute_app_command does on Iac

AI agents invoke execute_app_command to trigger actions in Iac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_app_command needs a policy

This tool executes arbitrary application commands on the user's system through AppleScript/JXA. While the description suggests it invokes 'app-specific actions', the broader server context (dynamic discovery and control of native macOS apps) and sibling tools (activate_app, click_element, send_keystroke, set_property) indicate this can trigger diverse side effects depending on which app and command are targeted.

From the tool's definition Tool name 'execute_app_command' and description 'Execute an application command' indicate code/command execution. Context shows it triggers app-specific actions on native macOS applications via AppleScript/JXA automation without pre-built safety controls.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_app_command Rate-limited

execute_app_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_app_command": {
      "limits": [
        {
          "counter": "execute_app_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Iac, so you can run agents against it safely.

FAQ

Questions about execute_app_command

What does the execute_app_command tool do? +

Execute an application command that was loaded via get_app_tools. Use this to invoke app-specific actions like activate, open, close, etc. First call get_app_tools to load the app\. It is categorised as a Execute tool in the Iac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_app_command? +

Register the Iac MCP server in PolicyLayer and add a rule for execute_app_command: 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 Iac. Nothing to install.

What risk level is execute_app_command? +

execute_app_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_app_command? +

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

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

execute_app_command is provided by the Iac MCP server (jsavin/iac-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.