is_wordpress_installed

Check if WordPress is installed on a hosting package

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/is-wordpress-installed.md

WHAT IT DOES

What is_wordpress_installed does on 20i MCP Server

AI agents call is_wordpress_installed to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why is_wordpress_installed is rated Low

This tool retrieves information about whether WordPress is installed on a hosting package. It performs a read-only check with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could only gather information about the hosting environment. No write, destructive, execute, or financial operations are possible.

From the tool's definition Tool name 'is_wordpress_installed' and description 'Check if WordPress is installed' indicate a query/status check operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs is_wordpress_installed safely

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

is_wordpress_installed Allowed

is_wordpress_installed is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "is_wordpress_installed": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every is_wordpress_installed call is checked against it from then on.

FAQ

Questions about is_wordpress_installed

What does the is_wordpress_installed tool do? +

Check if WordPress is installed on a hosting package. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on is_wordpress_installed? +

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

What risk level is is_wordpress_installed? +

is_wordpress_installed is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit is_wordpress_installed? +

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

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

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

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →