pressable_install_plugin · Pressable MCP Server MCP

WHAT IT DOES

What pressable_install_plugin does on Pressable MCP Server

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

Installing and activating a plugin executes code on the target WordPress site. This is an Execute-level action because it triggers an external operation (plugin installation and activation) that runs third-party code on the server. Misuse could introduce malicious plugins, backdoors, or unstable code, making the blast radius high.

From the tool's definition Install and activate a plugin on a site

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pressable_install_plugin Rate-limited

pressable_install_plugin 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": {
    "pressable_install_plugin": {
      "limits": [
        {
          "counter": "pressable_install_plugin_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 Pressable MCP Server, so you can run agents against it safely.

FAQ

Questions about pressable_install_plugin

What does the pressable_install_plugin tool do? +

Install and activate a plugin on a site. It is categorised as a Execute tool in the Pressable 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 pressable_install_plugin? +

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

What risk level is pressable_install_plugin? +

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

Can I rate-limit pressable_install_plugin? +

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

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

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