run_health_check · Sangfor Mcp Workflow MCP: Risk & Policy

WHAT IT DOES

What run_health_check does on Sangfor Mcp Workflow

AI agents invoke run_health_check to trigger actions in Sangfor Mcp Workflow. 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.

WHY IT NEEDS A POLICY

Why run_health_check needs a policy

The tool runs an active health check against real (production) network devices ('실장비' = real/live equipment), querying policy and status information. This is not a passive read from a database but an active operation executed against live infrastructure. Misuse or malfunction could disrupt device operation or expose sensitive configuration data.

From the tool's definition 'run_health_check' and '실장비 정책 상태 확인' (translates to 'check real device policy status') — triggers an active check against live equipment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_health_check Rate-limited

run_health_check 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_health_check": {
      "limits": [
        {
          "counter": "run_health_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sangfor Mcp Workflow, so you can run agents against it safely.

FAQ

Questions about run_health_check

What does the run_health_check tool do? +

실장비 정책 상태 확인. It is categorised as a Execute tool in the Sangfor Mcp Workflow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_health_check? +

Register the Sangfor Mcp Workflow MCP server in PolicyLayer and add a rule for run_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 Sangfor Mcp Workflow. Nothing to install.

What risk level is run_health_check? +

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

Can I rate-limit run_health_check? +

Yes. Add a rate_limit block to the run_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.

How do I block run_health_check completely? +

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

What MCP server provides run_health_check? +

run_health_check is provided by the Sangfor Mcp Workflow MCP server (whelp99-code/sangfor-mcp-workflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.