admin_get_user
Ruft detaillierte Informationen zu einem Benutzer ab
This record as markdown: /tools/c-sakel-wp-mcp-server/admin-get-user.md
What admin_get_user does on WordPress MCP Server
AI agents call admin_get_user to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why admin_get_user is rated Low
The tool retrieves user information without any side effects. It is a read-only operation that queries existing data. While it may expose sensitive user details, the classification reflects the tool's action (read) rather than potential misuse; severity is low because retrieving user metadata is a standard administrative function. No data is modified, deleted, or destroyed.
From the tool's definition Tool name 'admin_get_user' and description 'Ruft detaillierte Informationen zu einem Benutzer ab' (retrieves detailed information about a user) indicate a data retrieval operation with no modification, deletion, or execution of commands.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin_get_user, this is the rule to start with:
admin_get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every admin_get_user call is checked against it from then on.
Questions about admin_get_user
Ruft detaillierte Informationen zu einem Benutzer ab. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for admin_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 MCP Server. Nothing to install.
admin_get_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the admin_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.
Set action: deny in the PolicyLayer policy for admin_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.
admin_get_user is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue