Search WordPress posts and pages by keyword. Returns matching posts with titles, URLs, status, and excerpts.
AI agents call search_content to retrieve information from Noleemits Vision Builder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing WordPress content based on search criteria. It returns read-only metadata (titles, URLs, status, excerpts) without creating, modifying, deleting, or executing any actions. The operation is non-destructive and has no side effects beyond information retrieval, making it a Read category tool with low severity.
From the tool's definition Tool name 'search_content' and description 'Search WordPress posts and pages by keyword. Returns matching posts with titles, URLs, status, and excerpts.' indicate a query/retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
Search WordPress posts and pages by keyword. Returns matching posts with titles, URLs, status, and excerpts. It is categorised as a Read tool in the Noleemits Vision Builder MCP MCP Server, which means it retrieves data without modifying state.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for search_content: 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 Noleemits Vision Builder MCP. Nothing to install.
search_content 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 search_content 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 search_content. 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.
search_content is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-mcp). 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 →