ss_command

Send an SS-owned native command through the canonical MoteBus route.

SERVERUltra MCP-SS SOURCEmotebus/ultra-mcp-ss

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/motebus-ultra-mcp-ss/ss-command.md

WHAT IT DOES

What ss_command does on Ultra MCP-SS

AI agents invoke ss_command to trigger actions in Ultra MCP-SS. 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 ss_command is rated High

Executes arbitrary native commands on remote display hardware via MoteBus routing.

From the tool's definition Send an SS-owned native command through the canonical MoteBus route

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ss_command safely

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

ss_command Rate-limited

ss_command 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": {
    "ss_command": {
      "limits": [
        {
          "counter": "ss_command_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 Ultra MCP-SS, apply this rule, and every ss_command call is checked against it from then on.

FAQ

Questions about ss_command

What does the ss_command tool do? +

Send an SS-owned native command through the canonical MoteBus route. It is categorised as a Execute tool in the Ultra MCP-SS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ss_command? +

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

What risk level is ss_command? +

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

Can I rate-limit ss_command? +

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

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

ss_command is provided by the Ultra MCP-SS MCP server (motebus/ultra-mcp-ss). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ultra MCP-SS, and thousands of servers like it.

This server

All 18 Ultra MCP-SS tools → High-risk tools on this server →

Across the catalogue

adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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