toolmux_pipeline · Mcp Toolmux MCP: Risk & Policy

WHAT IT DOES

What toolmux_pipeline does on Mcp Toolmux

AI agents invoke toolmux_pipeline to trigger actions in Mcp Toolmux. 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 toolmux_pipeline needs a policy

This tool acts as an executor that chains multiple downstream MCP tool calls together. While it doesn't directly perform destructive or financial operations, it enables execution of arbitrary operations through downstream tools with input mapping control.

From the tool's definition Tool description states it can 'Run dependent downstream MCP tool calls serially with input mapping.' This enables execution of arbitrary downstream tools in sequence with data flow between them, which constitutes code/operation execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toolmux_pipeline Rate-limited

toolmux_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": {
    "toolmux_pipeline": {
      "limits": [
        {
          "counter": "toolmux_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 Mcp Toolmux, so you can run agents against it safely.

FAQ

Questions about toolmux_pipeline

What does the toolmux_pipeline tool do? +

Run dependent downstream MCP tool calls serially with input mapping. It is categorised as a Execute tool in the Mcp Toolmux MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on toolmux_pipeline? +

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

What risk level is toolmux_pipeline? +

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

Can I rate-limit toolmux_pipeline? +

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

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

toolmux_pipeline is provided by the Mcp Toolmux MCP server (mxz-dddd/mcp-toolmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.