run_pipeline · Portfolio Rotation MCP Server MCP

WHAT IT DOES

What run_pipeline does on Portfolio Rotation MCP Server

AI agents invoke run_pipeline to trigger actions in Portfolio Rotation MCP Server. 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_pipeline needs a policy

The tool performs computation and execution of sequential financial analysis operations (scoring, comparison, backtesting, stress testing) as indicated by sibling tools. While it operates on existing portfolio data (not creating irreversible changes to actual holdings), it executes complex algorithmic workflows whose outcomes depend on input parameters and could influence financial decisions.

From the tool's definition Tool name 'run_pipeline' on a portfolio rotation server that performs 'portfolio rotation analysis' with 'backtests' and 'risk checks'. The context shows this server scores holdings, identifies swaps, and validates strategies.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_pipeline Rate-limited

run_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": {
    "run_pipeline": {
      "limits": [
        {
          "counter": "run_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 Portfolio Rotation MCP Server, so you can run agents against it safely.

FAQ

Questions about run_pipeline

What does the run_pipeline tool do? +

run_pipeline. It is categorised as a Execute tool in the Portfolio Rotation MCP Server 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_pipeline? +

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

What risk level is run_pipeline? +

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

Can I rate-limit run_pipeline? +

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

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

run_pipeline is provided by the Portfolio Rotation MCP Server MCP server (mothanaprime/rebalance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.