create_shell_script_task · Morpheus MCP Server MCP

WHAT IT DOES

What create_shell_script_task does on Morpheus MCP Server

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

Despite the empty description, the name strongly suggests this tool creates shell script tasks within Morpheus, which can later be executed against cloud infrastructure. Shell scripts in an infrastructure management context carry high risk as they can run arbitrary commands across managed systems. The 'Execute' category fits because creating a shell script task is an action that sets up executable code.

From the tool's definition Tool name 'create_shell_script_task' implies creation of a shell script task; in the context of Morpheus MCP Server which 'execute workflows' and 'perform administrative tasks', shell script tasks are executable automation artifacts

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_shell_script_task Rate-limited

create_shell_script_task 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": {
    "create_shell_script_task": {
      "limits": [
        {
          "counter": "create_shell_script_task_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 create_shell_script_task

What does the create_shell_script_task tool do? +

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

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

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

Can I rate-limit create_shell_script_task? +

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

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

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