wait_for_execution · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What wait_for_execution does on Morpheus MCP Server

AI agents invoke wait_for_execution 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 wait_for_execution needs a policy

The tool's purpose—waiting for an execution to complete—indicates it participates in an execution flow within an HPE Morpheus cloud infrastructure management system. While the tool itself may not directly run code, it orchestrates the completion of potentially high-impact infrastructure operations (resource provisioning, workflow execution).

From the tool's definition Tool name 'wait_for_execution' indicates it blocks on or monitors the completion of an execution operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_execution Rate-limited

wait_for_execution 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": {
    "wait_for_execution": {
      "limits": [
        {
          "counter": "wait_for_execution_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 wait_for_execution

What does the wait_for_execution tool do? +

wait_for_execution. 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 wait_for_execution? +

Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for wait_for_execution: 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 wait_for_execution? +

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

Can I rate-limit wait_for_execution? +

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

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

wait_for_execution 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.

// THE FULL RECORD

wait_for_execution is one line of Morpheus MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →