legal_consent_log_stats
Aggregate consent decision counts by action and banner_version over a day range [from, to) (both optional, default the last 30 days including today; at most 366 days). Returns { from, to, rows: [{ action, banner_version, count }] }. Requires manage_options. Logging itself stays off until legal_pu...
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/legal-consent-log-stats.md
What legal_consent_log_stats does on Wordpress
AI agents call legal_consent_log_stats 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.
Why legal_consent_log_stats is rated Low
Tool retrieves and aggregates historical consent data without creating, modifying, or deleting information.
From the tool's definition Aggregate consent decision counts, returns statistics, no modifications
Attacks that exploit this kind of access
The rule that runs legal_consent_log_stats 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 legal_consent_log_stats, this is the rule to start with:
legal_consent_log_stats 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, apply this rule, and every legal_consent_log_stats call is checked against it from then on.
Questions about legal_consent_log_stats
Aggregate consent decision counts by action and banner_version over a day range [from, to) (both optional, default the last 30 days including today; at most 366 days). Returns { from, to, rows: [{ action, banner_version, count }] }. Requires manage_options. Logging itself stays off until legal_put_consent. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for legal_consent_log_stats: 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.
legal_consent_log_stats 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 legal_consent_log_stats 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 legal_consent_log_stats. 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.
legal_consent_log_stats 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.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue