setup_local_mcp

Single-target operation

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

// WHEN AI AGENTS USE THIS TOOL

AI agents use setup_local_mcp to create or modify resources in Local MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON SETUP_LOCAL_MCP

Without a policy, an AI agent could call setup_local_mcp repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Local MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

local-mcp-local-mcp.yaml

tools:
  setup_local_mcp:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Local MCP policy for all 7 tools.

// DETAILS

Tool Name setup_local_mcp

Category Write

MCP Server Local MCP MCP Server

Risk Level Medium

// MORE LOCAL MCP TOOLS

Write help Write report_issue Write request_feature Write send_logs Write troubleshoot Read get_status

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

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

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the setup_local_mcp tool do? +

Returns personalized install instructions for Local MCP. IMPORTANT: Ask the user for their email FIRST, then call this with email='their@email.com'. This generates a single command that installs AND auto-connects — no tray interaction needed. Pass 'step' or 'issue' for targeted troubleshooting help.. It is categorised as a Write tool in the Local MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_local_mcp? +

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

What risk level is setup_local_mcp? +

setup_local_mcp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_local_mcp? +

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

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

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

setup_local_mcp

Enforce policies on Local MCP