execute_task_on_instance · Morpheus MCP Server MCP

WHAT IT DOES

What execute_task_on_instance does on Morpheus MCP Server

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

This tool executes arbitrary tasks on instances within HPE Morpheus cloud infrastructure. Execution tools carry high severity due to their potential for unintended side effects and arbitrary code execution. The blast radius is significant—an AI agent could inadvertently run destructive commands, access sensitive data, or disrupt production workloads.

From the tool's definition Tool name 'execute_task_on_instance' indicates execution of tasks on cloud infrastructure instances. Server description states it 'enables users to provision resources, execute workflows, and perform administrative tasks'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_task_on_instance Rate-limited

execute_task_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": {
    "execute_task_on_instance": {
      "limits": [
        {
          "counter": "execute_task_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 execute_task_on_instance

What does the execute_task_on_instance tool do? +

execute_task_on_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 execute_task_on_instance? +

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

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

Can I rate-limit execute_task_on_instance? +

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

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

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