Full-text search across blog post titles, content, and excerpts.
AI agents call blog_search to retrieve information from Mcp Bot Crawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries blog data without side effects. It is a read-only operation that searches existing content. The blast radius of misuse is minimal—an agent could retrieve blog posts or metadata, but cannot modify, delete, or execute code. Low severity assigned due to limited sensitive data exposure typical of blog content.
From the tool's definition Tool performs 'Full-text search' across 'blog post titles, content, and excerpts' with no modification or execution capabilities described.
Attacks that exploit this kind of access
Full-text search across blog post titles, content, and excerpts. It is categorised as a Read tool in the Mcp Bot Crawler MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for blog_search: 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 Bot Crawler. Nothing to install.
blog_search 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 blog_search 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 blog_search. 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.
blog_search is provided by the Mcp Bot Crawler MCP server (merulocal/hellogrowthcrmwebsite_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 →