AI agents call wp_get_connected_users to retrieve information from WP Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty tool description, the server's read-only constraint and consistent pattern of sibling tools that retrieve WordPress data relationships (posts, comments, terms, schema) establish this as a retrieval operation. The 'get' verb and '_connected_' pattern match sibling relationship-mapping functions. No side effects, modifications, or destructive operations are possible on a read-only server.
From the tool's definition Server is explicitly 'read-only' with 'safe SQL querying' and all sibling tools (wp_get_post_meta, wp_get_post_terms, wp_get_relationships, etc.) are read operations. Tool name 'wp_get_connected_users' uses 'get' verb indicating data retrieval.
Documented attack patterns abuse exactly the kind of access wp_get_connected_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Database MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_get_connected_users:
{
"version": "1",
"default": "deny",
"tools": {
"wp_get_connected_users": {}
}
}wp_get_connected_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
wp_get_connected_users. It is categorised as a Read tool in the WP Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WP Database MCP Server MCP server in PolicyLayer and add a rule for wp_get_connected_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 WP Database MCP Server. Nothing to install.
wp_get_connected_users 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 wp_get_connected_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.
Set action: deny in the PolicyLayer policy for wp_get_connected_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.
wp_get_connected_users is provided by the WP Database MCP Server MCP server (s3rgiosan/wp-db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Database MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 WP Database MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.