birst_run_workflow · Infor Birst MCP Server MCP

WHAT IT DOES

What birst_run_workflow does on Infor Birst MCP Server

AI agents invoke birst_run_workflow to trigger actions in Infor Birst 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 birst_run_workflow needs a policy

The tool executes a workflow on demand, which is an Execute category action. While the server also includes Destructive tools (delete_* operations), this specific tool only triggers execution. Severity is high because workflows can have broad side effects across data systems, integrations, and dependent processes, though without evidence of financial impact or irreversible data deletion, it does not reach critical.

From the tool's definition Tool description states it 'trigger[s] a workflow to run immediately', which initiates external operations whose effects depend on arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

birst_run_workflow Rate-limited

birst_run_workflow 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": {
    "birst_run_workflow": {
      "limits": [
        {
          "counter": "birst_run_workflow_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 Infor Birst MCP Server, so you can run agents against it safely.

FAQ

Questions about birst_run_workflow

What does the birst_run_workflow tool do? +

Trigger a workflow to run immediately. Returns the run ID for status monitoring. It is categorised as a Execute tool in the Infor Birst 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 birst_run_workflow? +

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

What risk level is birst_run_workflow? +

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

Can I rate-limit birst_run_workflow? +

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

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

birst_run_workflow is provided by the Infor Birst MCP Server MCP server (mikahdev/infor-birst-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.