acf_get_user_fields
Ruft ACF Custom Fields eines Benutzers ab
This record as markdown: /tools/c-sakel-wp-mcp-server/acf-get-user-fields.md
What acf_get_user_fields does on WordPress MCP Server
AI agents call acf_get_user_fields 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 acf_get_user_fields is rated Low
This tool retrieves user field data from Advanced Custom Fields (ACF) without modifying, deleting, or executing any operations. It is a simple data retrieval function. The only potential concern would be information disclosure if sensitive user fields are exposed, but that is inherent to any read operation on user data and does not elevate this beyond the 'Read' category.
From the tool's definition Tool name is 'acf_get_user_fields' and description states 'Ruft ACF Custom Fields eines Benutzers ab' (Retrieves ACF Custom Fields of a user). The verb 'get/retrieves' indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
The rule that runs acf_get_user_fields 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 acf_get_user_fields, this is the rule to start with:
acf_get_user_fields 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 acf_get_user_fields call is checked against it from then on.
Questions about acf_get_user_fields
Ruft ACF Custom Fields eines Benutzers 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 acf_get_user_fields: 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.
acf_get_user_fields 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 acf_get_user_fields 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 acf_get_user_fields. 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.
acf_get_user_fields 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