Upload media files to WordPress from local paths or URLs
AI agents use upload-media 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.
Uploading media creates new resources in WordPress but is reversible (media can be deleted afterward), making it a Write operation rather than Execute or Destructive. Severity is high because uncontrolled media uploads could fill storage, introduce malicious files, or deface the site through injected content, though the blast radius is somewhat limited compared to publishing or user administration.
From the tool's definition Tool description states it uploads media files to WordPress, which creates new data in the WordPress system.
Documented attack patterns abuse exactly the kind of access upload-media 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 upload-media:
{
"version": "1",
"default": "deny",
"tools": {
"upload-media": {
"limits": [
{
"counter": "upload-media_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload-media 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.
Upload media files to WordPress from local paths or URLs. 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 upload-media: 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.
upload-media 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 upload-media 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 upload-media. 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.
upload-media 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.