Finds content by its URL, automatically detecting the content type, and optionally updates it
AI agents call find_content_by_url to retrieve information from mcp-wordpress-instaWP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's primary purpose is to search for and retrieve content by URL without changing state. While it mentions optional updates, the 'find' verb and retrieval-focused description indicate this is a Read operation. Even if updates are possible, the tool's name and default behavior suggest querying/fetching is the main use case.
From the tool's definition Tool is named 'find_content_by_url' and its description states it 'Finds content by its URL, automatically detecting the content type.' This is fundamentally a retrieval operation.
Attacks that exploit this kind of access
Finds content by its URL, automatically detecting the content type, and optionally updates it. It is categorised as a Read tool in the mcp-wordpress-instaWP MCP Server, which means it retrieves data without modifying state.
Register the mcp-wordpress-instaWP MCP server in PolicyLayer and add a rule for find_content_by_url: 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 mcp-wordpress-instaWP. Nothing to install.
find_content_by_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_content_by_url 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 find_content_by_url. 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.
find_content_by_url is provided by the mcp-wordpress-instaWP MCP server (pace8/mcp-wordpress). 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 →