seo_list_monitor_log

List the 404 monitor log: { items: [{ id, url, hits, first_seen, last_seen, ... }], total, pages }.

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/seo-list-monitor-log.md

WHAT IT DOES

What seo_list_monitor_log does on Wordpress

AI agents call seo_list_monitor_log to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why seo_list_monitor_log is rated Low

Tool retrieves and lists existing 404 monitoring log entries; no data modification or side effects.

From the tool's definition List the 404 monitor log; retrieves log data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seo_list_monitor_log safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo_list_monitor_log, this is the rule to start with:

seo_list_monitor_log Allowed

seo_list_monitor_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "seo_list_monitor_log": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every seo_list_monitor_log call is checked against it from then on.

FAQ

Questions about seo_list_monitor_log

What does the seo_list_monitor_log tool do? +

List the 404 monitor log: { items: [{ id, url, hits, first_seen, last_seen, ... }], total, pages }. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on seo_list_monitor_log? +

Register the Wordpress MCP server in PolicyLayer and add a rule for seo_list_monitor_log: 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. Nothing to install.

What risk level is seo_list_monitor_log? +

seo_list_monitor_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit seo_list_monitor_log? +

Yes. Add a rate_limit block to the seo_list_monitor_log 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.

How do I block seo_list_monitor_log completely? +

Set action: deny in the PolicyLayer policy for seo_list_monitor_log. 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.

What MCP server provides seo_list_monitor_log? +

seo_list_monitor_log is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →