update_self_diagnosis
Returns the self-update health state: current version, last N update attempts (with errors), writability of the update cache, and any stale LMCP binaries found at alternate paths. Call this when auto-update seems stuck or when you need to explain to a user why they're on an old version.
This record as markdown: /tools/com-local-mcp-local-mcp/update-self-diagnosis.md
What update_self_diagnosis does on Local
AI agents call update_self_diagnosis to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max recent attempts to return (default 10) |
Parameters from the server's own tool schema.
Why update_self_diagnosis is rated Low
The tool only reads and returns diagnostic information about the update system (version, attempt history, cache writability, binary paths). It does not modify, delete, or execute anything; it is purely a read/query operation.
From the tool's definition Returns the self-update health state: current version, last N update attempts (with errors), writability of the update cache, and any stale LMCP binaries found at alternate paths
Attacks that exploit this kind of access
The rule that runs update_self_diagnosis 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_self_diagnosis, this is the rule to start with:
update_self_diagnosis is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every update_self_diagnosis call is checked against it from then on.
Questions about update_self_diagnosis
Returns the self-update health state: current version, last N update attempts (with errors), writability of the update cache, and any stale LMCP binaries found at alternate paths. Call this when auto-update seems stuck or when you need to explain to a user why they're on an old version. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
update_self_diagnosis accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for update_self_diagnosis: 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.
update_self_diagnosis is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the update_self_diagnosis 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.
Set action: deny in the PolicyLayer policy for update_self_diagnosis. 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.
update_self_diagnosis 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.
More on Local, and thousands of servers like it.
This server
Across the catalogue