AI agents use wp_media_import to create or update resources in Wp Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wp Cli environment.
The tool creates/writes new data (media files) to the WordPress database and filesystem. While it does not delete or overwrite existing media (which would be Destructive), and does not directly execute arbitrary code or trigger external side effects dependent on malicious arguments (which would be Execute), it does irreversibly add data.
From the tool's definition Tool is named 'wp_media_import' with description 'Import media from URL' — this creates new media assets in WordPress by fetching and storing content from an external source.
Attacks that exploit this kind of access
Import media from URL. It is categorised as a Write tool in the Wp Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_media_import: 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 Cli. Nothing to install.
wp_media_import 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 wp_media_import 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 wp_media_import. 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.
wp_media_import is provided by the Wp Cli MCP server (mvtandas/wp-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
wp_media_import is one line of Wp Cli's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →