AI agents call get-referrers to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves referrer information (HTTP referrer data showing which external sites sent traffic to the WordPress site). It performs a query/read operation with no side effects, no data modification, and no execution of external operations. It aligns with the 'Read' category as a retrieval function. Severity is low because referrer data is typically non-sensitive site analytics information.
From the tool's definition Tool name 'get-referrers' and description 'View a site' indicate data retrieval with no modification. The sibling context shows this is part of a WordPress analytics/traffic tool set (get-clicks, get-referrers) that queries existing data.
Documented attack patterns abuse exactly the kind of access get-referrers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-referrers:
{
"version": "1",
"default": "deny",
"tools": {
"get-referrers": {}
}
}get-referrers 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.
View a site. 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 get-referrers: 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.
get-referrers 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 get-referrers 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 get-referrers. 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.
get-referrers is provided by the WordPress MCP Server MCP server (prathammanocha/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.