New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

legal_consent_log_export

Export the raw consent decision log as CSV for a day range (same optional from/to rules as legal_consent_log_stats). Returns { filename, csv }; the csv is the full file text, ready to write out as-is. Requires manage_options. Logging itself stays off until legal_put_consent

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/legal-consent-log-export.md

What legal_consent_log_export does on Wordpress

AI agents use legal_consent_log_export to create or update resources in Wordpress, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wordpress environment.

Why legal_consent_log_export is rated Medium

An AI agent can call legal_consent_log_export faster than any human can review: one bad instruction and it creates or modifies resources in Wordpress by the hundred, each call as confident as the last.

Questions about legal_consent_log_export

What does the legal_consent_log_export tool do? +

Export the raw consent decision log as CSV for a day range (same optional from/to rules as legal_consent_log_stats). Returns { filename, csv }; the csv is the full file text, ready to write out as-is. Requires manage_options. Logging itself stays off until legal_put_consent. It is categorised as a Write tool in the Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on legal_consent_log_export? +

Register the Wordpress MCP server in PolicyLayer and add a rule for legal_consent_log_export: 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 legal_consent_log_export? +

legal_consent_log_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit legal_consent_log_export? +

Yes. Add a rate_limit block to the legal_consent_log_export 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 legal_consent_log_export completely? +

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

legal_consent_log_export 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Wordpress's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.