sitebay_wordpress_proxy · SiteBay MCP Server MCP

WHAT IT DOES

What sitebay_wordpress_proxy does on SiteBay MCP Server

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

A proxy tool forwards arbitrary HTTP requests to the WordPress site, meaning it can perform any operation the WordPress API or admin interface supports — including executing code, modifying content, or deleting data. The actual impact depends on the request being proxied, but the potential blast radius is high since it can be used to trigger any WordPress action.

From the tool's definition 'Proxy requests to a WordPress site' — proxies arbitrary requests to a WordPress site, which can trigger reads, writes, executes, or destructive operations depending on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sitebay_wordpress_proxy Rate-limited

sitebay_wordpress_proxy 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_wordpress_proxy": {
      "limits": [
        {
          "counter": "sitebay_wordpress_proxy_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_wordpress_proxy

What does the sitebay_wordpress_proxy tool do? +

Proxy requests to a WordPress site. 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_wordpress_proxy? +

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

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

Can I rate-limit sitebay_wordpress_proxy? +

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

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

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