检查 oMLX、VLM、MinerU、PaddleOCR、Qwen3-ASR、ffmpeg、Playwright、ADB 等组件的可用性。
AI agents call health_check to retrieve information from Local Mmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of local system components (oMLX, VLM, MinerU, PaddleOCR, Qwen3-ASR, ffmpeg, Playwright, ADB) to determine if they are available/functional. It is a diagnostic read-only operation with no side effects, no code execution triggered by arguments, and no data modification. The blast radius of misuse is minimal—at worst, an agent learns which components are unavailable.
From the tool's definition Tool name 'health_check' and description indicate it performs status checks on system components ('检查...可用性' = 'check...availability'). It retrieves component availability information without modifying, executing operations on, or deleting data.
Attacks that exploit this kind of access
检查 oMLX、VLM、MinerU、PaddleOCR、Qwen3-ASR、ffmpeg、Playwright、ADB 等组件的可用性。. It is categorised as a Read tool in the Local Mmcp MCP Server, which means it retrieves data without modifying state.
Register the Local M MCP server in PolicyLayer and add a rule for health_check: 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 Mmcp. Nothing to install.
health_check 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 health_check 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 health_check. 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.
health_check is provided by the Local M MCP server (rorojiao/local-mmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →