legal_render_document

Render a document to normalized HTML without saving. Useful to preview the heading hierarchy and slug ids before writing.

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/legal-render-document.md

WHAT IT DOES

What legal_render_document does on Wordpress

AI agents call legal_render_document 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 legal_render_document is rated Low

Reads and previews document structure without modifying or persisting data.

From the tool's definition Render document to normalized HTML without saving

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs legal_render_document 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_render_document, this is the rule to start with:

legal_render_document Allowed

legal_render_document 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": {
    "legal_render_document": {}
  }
}

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 legal_render_document call is checked against it from then on.

FAQ

Questions about legal_render_document

What does the legal_render_document tool do? +

Render a document to normalized HTML without saving. Useful to preview the heading hierarchy and slug ids before writing. 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 legal_render_document? +

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

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

Can I rate-limit legal_render_document? +

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

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

legal_render_document 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

The MCP Attack Database →

Guides

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