node_sms_send

Send an SMS message using an Android mobile companion device. Not available on iOS.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/node-sms-send.md

WHAT IT DOES

What node_sms_send does on CoWork OS

AI agents invoke node_sms_send to trigger actions in CoWork OS. 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.

RISK

Why node_sms_send is rated High

This tool sends real SMS messages to external recipients via a physical device. It triggers an external operation (SMS transmission) with real-world consequences — potential for spam, harassment, phishing, or unintended communication. While not financial or destructive, it executes an action with significant blast radius if misused by an AI agent.

From the tool's definition Send an SMS message using an Android mobile companion device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_sms_send safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_sms_send, this is the rule to start with:

node_sms_send Rate-limited

node_sms_send 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": {
    "node_sms_send": {
      "limits": [
        {
          "counter": "node_sms_send_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every node_sms_send call is checked against it from then on.

FAQ

Questions about node_sms_send

What does the node_sms_send tool do? +

Send an SMS message using an Android mobile companion device. Not available on iOS. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on node_sms_send? +

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

What risk level is node_sms_send? +

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

Can I rate-limit node_sms_send? +

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

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

node_sms_send is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →