cancel_pipeline · Lightrag MCP: Risk & Policy

WHAT IT DOES

What cancel_pipeline does on Lightrag

AI agents invoke cancel_pipeline to trigger actions in Lightrag. 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 cancel_pipeline needs a policy

This tool triggers an external operation (cancelling a running pipeline), which is an active intervention that affects system state. It is not merely reading data, nor does it delete/overwrite stored data irreversibly — it stops a running process. This best fits 'Execute' as it triggers an operational action whose effects depend on the current pipeline state.

From the tool's definition Request cancellation of the currently running pipeline

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cancel_pipeline Rate-limited

cancel_pipeline 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": {
    "cancel_pipeline": {
      "limits": [
        {
          "counter": "cancel_pipeline_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 Lightrag, so you can run agents against it safely.

FAQ

Questions about cancel_pipeline

What does the cancel_pipeline tool do? +

Request cancellation of the currently running pipeline. It is categorised as a Execute tool in the Lightrag MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cancel_pipeline? +

Register the Lightrag MCP server in PolicyLayer and add a rule for cancel_pipeline: 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 Lightrag. Nothing to install.

What risk level is cancel_pipeline? +

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

Can I rate-limit cancel_pipeline? +

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

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

cancel_pipeline is provided by the Lightrag MCP server (lightrag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.