Bulk rewrite media URLs in all exported content files. Replaces one domain with another (e.g., example.com → app.example.com for go-live).
AI agents use media_rewrite 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.
The tool modifies content (media URLs) across multiple files in a reversible manner. While rewriting is a mutation, it does not delete or irreversibly destroy data (ruling out Destructive), nor does it execute arbitrary code or external operations (ruling out Execute).
From the tool's definition Tool description explicitly states it 'Bulk rewrite media URLs in all exported content files' and 'Replaces one domain with another'. This modifies content files at scale.
Documented attack patterns abuse exactly the kind of access media_rewrite 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 media_rewrite:
{
"version": "1",
"default": "deny",
"tools": {
"media_rewrite": {
"limits": [
{
"counter": "media_rewrite_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}media_rewrite 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.
Bulk rewrite media URLs in all exported content files. Replaces one domain with another (e.g., example.com → app.example.com for go-live). 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 media_rewrite: 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.
media_rewrite 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 media_rewrite 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 media_rewrite. 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.
media_rewrite 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.