Update title, caption, alt text, and description of media files
AI agents use edit-media-metadata to create or update resources in AutoWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoWP MCP Server environment.
This tool creates or modifies media metadata in a WordPress site through the REST API. The changes are reversible (metadata can be edited again), and the operation does not delete files or execute arbitrary code. It falls squarely into the Write category.
From the tool's definition Tool updates metadata fields (title, caption, alt text, description) of media files, which modifies data reversibly without deletion or destruction.
Documented attack patterns abuse exactly the kind of access edit-media-metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for edit-media-metadata:
{
"version": "1",
"default": "deny",
"tools": {
"edit-media-metadata": {
"limits": [
{
"counter": "edit-media-metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit-media-metadata 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.
Update title, caption, alt text, and description of media files. It is categorised as a Write tool in the AutoWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoWP MCP Server MCP server in PolicyLayer and add a rule for edit-media-metadata: 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 AutoWP MCP Server. Nothing to install.
edit-media-metadata 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 edit-media-metadata 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 edit-media-metadata. 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.
edit-media-metadata is provided by the AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, 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.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.