Convert a single WordPress post to Astro Markdown. Returns full frontmatter + body with conversion issues report.
AI agents use convert_post to create or update resources in WP Astro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WP Astro MCP environment.
This tool creates new data (converted Markdown files with frontmatter) from source WordPress post data. While the conversion process itself is reversible and the original WordPress data remains intact, the tool produces new output artifacts that represent a modification of content into a different format and structure.
From the tool's definition Tool description states it 'Convert[s] a single WordPress post to Astro Markdown' and 'Returns full frontmatter + body', indicating it creates or modifies a converted content artifact.
Documented attack patterns abuse exactly the kind of access convert_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Astro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_post:
{
"version": "1",
"default": "deny",
"tools": {
"convert_post": {
"limits": [
{
"counter": "convert_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_post stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Convert a single WordPress post to Astro Markdown. Returns full frontmatter + body with conversion issues report. It is categorised as a Write tool in the WP Astro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WP Astro MCP server in PolicyLayer and add a rule for convert_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 WP Astro MCP. Nothing to install.
convert_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convert_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 convert_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.
convert_post is provided by the WP Astro MCP server (vapvarun/wp-astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Astro MCP, 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.
60 WP Astro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.