AI agents use wordpress_upload_media to create or update resources in ItchWPMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ItchWPMCP environment.
This tool creates new media assets in WordPress by uploading files. It is reversible (uploaded media can be deleted), so it falls under Write rather than Destructive. The severity is medium because uncontrolled uploads could fill storage, introduce malware, or pollute the media library, but the impact is limited to the media library and reversible.
From the tool's definition Tool name 'wordpress_upload_media' and description 'Upload a local file to the WordPress media library' indicate creating/adding new content to the system.
Attacks that exploit this kind of access
Upload a local file to the WordPress media library. It is categorised as a Write tool in the ItchWPMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_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 ItchWPMCP. Nothing to install.
wordpress_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 wordpress_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 wordpress_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.
wordpress_upload_media is provided by the ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →