sitebay_site_shell_command · SiteBay MCP Server MCP

WHAT IT DOES

What sitebay_site_shell_command does on SiteBay MCP Server

AI agents invoke sitebay_site_shell_command to trigger actions in SiteBay 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 sitebay_site_shell_command needs a policy

Shell command execution is a textbook Execute category tool. An AI agent with access to this could run any command on the server—install malware, exfiltrate data, modify files, or pivot to other infrastructure.

From the tool's definition Tool description explicitly states 'Execute a shell command on a WordPress site'. The ability to run arbitrary shell commands, including WP-CLI, provides unrestricted code execution on a hosted server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sitebay_site_shell_command Rate-limited

sitebay_site_shell_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": {
    "sitebay_site_shell_command": {
      "limits": [
        {
          "counter": "sitebay_site_shell_command_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 SiteBay MCP Server, so you can run agents against it safely.

FAQ

Questions about sitebay_site_shell_command

What does the sitebay_site_shell_command tool do? +

Execute a shell command on a WordPress site (supports WP-CLI). It is categorised as a Execute tool in the SiteBay 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 sitebay_site_shell_command? +

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

What risk level is sitebay_site_shell_command? +

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

Can I rate-limit sitebay_site_shell_command? +

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

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

sitebay_site_shell_command is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.