setup_install

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/setup-install.md

WHAT IT DOES

What setup_install does on Local

AI agents invoke setup_install to trigger actions in Local. 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.

Parameter	Type	Required	Description
`os`	string	Yes	macos \| windows \| linux \| ios \| android. Cloud connectors must pass os (or server asks). Desktop terminal clients may omit → macOS. Windows/Linux/mobile → waitl
`step`	string	—	If stuck: connector \| install \| email \| connecting_stuck \| server_down.
`email`	string	—	Optional. Helps Cloud Relay auto-connect after install.
`issue`	string	—	Optional tag: gatekeeper_error, dot_not_green, install_failed, etc.

Parameters from the server's own tool schema.

RISK

Why setup_install is rated High

This tool triggers an installation process on the user's machine, which constitutes executing an external operation with significant system-level effects. Installing software is irreversible in practice (system changes, new processes, data access grants) and could expose Mail, Calendar, Contacts, Teams, OneDrive, and more to the installed app. The instruction to 'Call this NOW' suggests urgency-driven execution.

From the tool's definition "Install LMCP — free Mac app" and "Call this NOW to show their personalized install link"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs setup_install safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setup_install, this is the rule to start with:

setup_install Rate-limited

setup_install 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": {
    "setup_install": {
      "limits": [
        {
          "counter": "setup_install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every setup_install call is checked against it from then on.

FAQ

Questions about setup_install

What does the setup_install tool do? +

Install LMCP — free Mac app giving the user access to Mail, Calendar, Contacts, Teams, OneDrive, Notes, Reminders, and 100+ tools on their Mac (data stays local). Call this NOW to show their personalized install link (~30 sec). Pass os="macos" unless they said otherwise (windows/linux/ios/android). Optional: email, step, issue. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does setup_install accept? +

setup_install accepts 4 parameters: os, step, email, issue. Required: os. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on setup_install? +

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

What risk level is setup_install? +

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

Can I rate-limit setup_install? +

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

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

setup_install is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →