send_message_to_node · Cluster Execution MCP Server MCP

WHAT IT DOES

What send_message_to_node does on Cluster Execution MCP Server

AI agents invoke send_message_to_node to trigger actions in Cluster Execution 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 send_message_to_node needs a policy

The tool name 'send_message_to_node' on a cluster execution server that supports SSH-based remote node management suggests it triggers inter-node communication that could initiate remote execution or command routing. In the context of this server, messages likely trigger actions on remote nodes. Description is empty, which lowers confidence.

From the tool's definition Tool name: send_message_to_node; Server context: cluster execution, remote node management via SSH, distributed nodes, parallel execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_message_to_node Rate-limited

send_message_to_node 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": {
    "send_message_to_node": {
      "limits": [
        {
          "counter": "send_message_to_node_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 Cluster Execution MCP Server, so you can run agents against it safely.

FAQ

Questions about send_message_to_node

What does the send_message_to_node tool do? +

send_message_to_node. It is categorised as a Execute tool in the Cluster Execution 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 send_message_to_node? +

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

What risk level is send_message_to_node? +

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

Can I rate-limit send_message_to_node? +

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

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

send_message_to_node is provided by the Cluster Execution MCP Server MCP server (marc-shade/cluster-execution-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.