wp_get_user

Get a user by ID

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/wp-get-user.md

WHAT IT DOES

What wp_get_user does on Wordpress

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

RISK

Why wp_get_user is rated Low

This tool retrieves user information by ID. It performs a read-only query operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal; an agent could learn user details but cannot cause damage. Classified as Read with low severity.

From the tool's definition Tool name is 'wp_get_user' and description states 'Get a user by ID' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_get_user safely

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

wp_get_user Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every wp_get_user call is checked against it from then on.

FAQ

Questions about wp_get_user

What does the wp_get_user tool do? +

Get a user by ID. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wp_get_user? +

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

What risk level is wp_get_user? +

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

Can I rate-limit wp_get_user? +

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

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

wp_get_user is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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