AI agents use report-referrer-spam to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.
Reporting a referrer as spam modifies site data by flagging/marking a referrer entry, which is a reversible write action (the report could potentially be undone or the referrer unblocked). It does not delete data irreversibly, execute code, or involve financial transactions. Severity is medium because misuse could incorrectly flag legitimate referrers, affecting site analytics or access.
From the tool's definition Report a referrer as spam
Documented attack patterns abuse exactly the kind of access report-referrer-spam 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 report-referrer-spam:
{
"version": "1",
"default": "deny",
"tools": {
"report-referrer-spam": {
"limits": [
{
"counter": "report-referrer-spam_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}report-referrer-spam stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Report a referrer as spam. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for report-referrer-spam: 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.
report-referrer-spam is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the report-referrer-spam 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 report-referrer-spam. 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.
report-referrer-spam 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.