get_wordpress_users

Get WordPress users for 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/get-wordpress-users.md

WHAT IT DOES

What get_wordpress_users does on 20i MCP Server

AI agents call get_wordpress_users 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 get_wordpress_users is rated Low

This tool retrieves WordPress user information from a hosting package without modifying, deleting, or executing operations. It is a read-only query operation. The severity is low because unauthorized access to WordPress user lists poses minimal immediate risk compared to modification or deletion tools on the same server (e.g., add_mssql_user, activate_package).

From the tool's definition Tool name 'get_wordpress_users' and description 'Get WordPress users for a hosting package' indicate data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_wordpress_users 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 get_wordpress_users, this is the rule to start with:

get_wordpress_users Allowed

get_wordpress_users 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": {
    "get_wordpress_users": {}
  }
}

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 get_wordpress_users call is checked against it from then on.

FAQ

Questions about get_wordpress_users

What does the get_wordpress_users tool do? +

Get WordPress users for 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 get_wordpress_users? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_wordpress_users: 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 get_wordpress_users? +

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

Can I rate-limit get_wordpress_users? +

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

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

get_wordpress_users 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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