run_workflow_on_instance · Morpheus MCP Server MCP

WHAT IT DOES

What run_workflow_on_instance does on Morpheus MCP Server

AI agents invoke run_workflow_on_instance to trigger actions in Morpheus 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_workflow_on_instance needs a policy

This tool invokes arbitrary workflows on cloud infrastructure instances. The outcome is entirely dependent on what workflow is specified and its implementation, making it a classic Execute operation. While it could potentially be destructive (if a workflow deletes data) or financial (if a workflow triggers billing changes), the tool description itself only indicates execution capability.

From the tool's definition 'Execute a workflow against a specific instance' describes triggering external operations whose effects depend on arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_workflow_on_instance Rate-limited

run_workflow_on_instance 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_workflow_on_instance": {
      "limits": [
        {
          "counter": "run_workflow_on_instance_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 Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about run_workflow_on_instance

What does the run_workflow_on_instance tool do? +

Execute a workflow against a specific instance. It is categorised as a Execute tool in the Morpheus 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_workflow_on_instance? +

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

What risk level is run_workflow_on_instance? +

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

Can I rate-limit run_workflow_on_instance? +

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

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

run_workflow_on_instance is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.