Read any WordPress post by ID without opening it for editing. Returns the saved (committed) content as a block listing. Use this to research other posts while keeping the current post open.
AI agents call wp_view_post to retrieve information from Claudaborative Editing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing post content without modification, creation, or deletion. It is a pure read operation that returns data in a non-destructive manner. The blast radius of misuse is minimal, as an AI agent could only view posts it has authorization to read, not alter them.
From the tool's definition Tool name 'wp_view_post' and description 'Read any WordPress post by ID without opening it for editing. Returns the saved (committed) content as a block listing.' — explicitly states 'Read' and 'without opening it for editing', indicating query-only retrieval…
Documented attack patterns abuse exactly the kind of access wp_view_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claudaborative Editing, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_view_post:
{
"version": "1",
"default": "deny",
"tools": {
"wp_view_post": {}
}
}wp_view_post is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read any WordPress post by ID without opening it for editing. Returns the saved (committed) content as a block listing. Use this to research other posts while keeping the current post open. It is categorised as a Read tool in the Claudaborative Editing MCP Server, which means it retrieves data without modifying state.
Register the Claudaborative Editing MCP server in PolicyLayer and add a rule for wp_view_post: 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 Claudaborative Editing. Nothing to install.
wp_view_post 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 wp_view_post 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 wp_view_post. 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.
wp_view_post is provided by the Claudaborative Editing MCP server (pento/claudaborative-editing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claudaborative Editing, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Claudaborative Editing tools catalogued and risk-classified — across an index of 43,000+ MCP servers.