High Risk →

classic_mac_launch_app

Launch an application on the Classic Mac by path or creator code. Creator codes are 4-character identifiers (e.g. 'ttxt' for SimpleText, 'WILD' for HyperCard). Requires AgentBridge.

Accepts file system path (path)

Part of the Classic Mac MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

classic-mac-mcp Execute Risk 4/5

AI agents invoke classic_mac_launch_app to trigger processes or run actions in Classic Mac. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

classic_mac_launch_app can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-seanfdz-agentbridge.yaml
tools:
  classic_mac_launch_app:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Classic Mac policy for all 23 tools.

Tool Name classic_mac_launch_app
Category Execute
Risk Level High

View all 23 tools →

Agents calling execute-class tools like classic_mac_launch_app have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

classic_mac_launch_app is one of the high-risk operations in Classic Mac. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the classic_mac_launch_app tool do? +

Launch an application on the Classic Mac by path or creator code. Creator codes are 4-character identifiers (e.g. 'ttxt' for SimpleText, 'WILD' for HyperCard). Requires AgentBridge.. It is categorised as a Execute tool in the Classic Mac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on classic_mac_launch_app? +

Add a rule in your Intercept YAML policy under the tools section for classic_mac_launch_app. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Classic Mac MCP server.

What risk level is classic_mac_launch_app? +

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

Can I rate-limit classic_mac_launch_app? +

Yes. Add a rate_limit block to the classic_mac_launch_app rule in your Intercept 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 classic_mac_launch_app completely? +

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

classic_mac_launch_app is provided by the Classic Mac MCP server (classic-mac-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Classic Mac

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.