run_diagnostics

Runs a fast health check of all LMCP integrations on this machine. Shows what works, what doesn't, and how to fix it. Optionally submits a report to the LMCP team.

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/run-diagnostics.md

WHAT IT DOES

What run_diagnostics does on Local

AI agents invoke run_diagnostics 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
`focus`	string	—	Integration to focus on: calendar, mail, contacts, reminders, omnifocus, outlook, notes, finder, onedrive. Leave empty to check all.
`submit`	boolean	—	Send the diagnostic report to the LMCP team for analysis (default: false)

Parameters from the server's own tool schema.

RISK

Why run_diagnostics is rated High

This tool executes diagnostic operations on the local system to check LMCP integration health. While not destructive or directly modifying data, it performs active system operations and can optionally transmit diagnostic reports externally. The 'run' verb and the act of executing health checks and potential report submission to external parties (LMCP team) classifies this as Execute rather than Read.

From the tool's definition Tool name 'run_diagnostics' and description 'Runs a fast health check' and 'Optionally submits a report' indicate execution of diagnostic operations and potential network transmission of system state information.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

run_diagnostics Rate-limited

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

FAQ

Questions about run_diagnostics

What does the run_diagnostics tool do? +

Runs a fast health check of all LMCP integrations on this machine. Shows what works, what doesn't, and how to fix it. Optionally submits a report to the LMCP team. 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 run_diagnostics accept? +

run_diagnostics accepts 2 parameters: focus, submit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_diagnostics? +

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

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

Can I rate-limit run_diagnostics? +

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

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

run_diagnostics 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

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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