Diagnose the server environment: check if the OrcaSlicer binary is reachable and if the settings/work directories are accessible.
AI agents call health_check to retrieve information from OrcaSlicer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
health_check is a diagnostic/status verification tool. It retrieves information about system accessibility and binary availability—classic read operations. There are no side effects, no data modifications, no destructive actions, and no code execution triggered by the check itself. The low severity reflects that misuse would only return false status information, not cause harm.
From the tool's definition The tool performs diagnostic checks: 'check if the OrcaSlicer binary is reachable and if the settings/work directories are accessible.' These are queries that verify system state without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Diagnose the server environment: check if the OrcaSlicer binary is reachable and if the settings/work directories are accessible. It is categorised as a Read tool in the OrcaSlicer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OrcaSlicer MCP Server 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 OrcaSlicer MCP Server. 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 OrcaSlicer MCP Server MCP server (itsumonotakumi/orcaslicer-mcp). 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 →