update_local_mcp

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 20 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/update-local-mcp.md

WHAT IT DOES

What update_local_mcp does on Local

AI agents invoke update_local_mcp 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
`confirm`	boolean	—	Must be true to actually install (which restarts LMCP). Without it, returns availability + a preview.
`check_only`	boolean	—	If true, only report availability — no download, no install, no restart.

Parameters from the server's own tool schema.

RISK

Why update_local_mcp is rated High

This tool downloads and installs software updates and restarts the MCP service, which constitutes executing an external operation with system-level side effects. It modifies the running software environment and disrupts active connections. While it has a confirmation gate, misuse could destabilize the AI client connection or install unintended versions.

From the tool's definition 'installs LMCP updates', 'downloads the update and RESTARTS LMCP', 'requires confirm=true'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_local_mcp 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 update_local_mcp, this is the rule to start with:

update_local_mcp Rate-limited

update_local_mcp 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": {
    "update_local_mcp": {
      "limits": [
        {
          "counter": "update_local_mcp_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 update_local_mcp call is checked against it from then on.

FAQ

Questions about update_local_mcp

What does the update_local_mcp tool do? +

Checks for and installs LMCP updates. Installing downloads the update and RESTARTS LMCP (the AI client briefly reconnects), so it requires confirm=true. Pass check_only=true to only report whether an update is available, with no download or restart. 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 update_local_mcp accept? +

update_local_mcp accepts 2 parameters: confirm, check_only. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_local_mcp? +

Register the Local MCP server in PolicyLayer and add a rule for update_local_mcp: 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 update_local_mcp? +

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

Can I rate-limit update_local_mcp? +

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

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

update_local_mcp 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 →