Search blog posts by query, category, or tags
AI agents call search_posts to retrieve information from Jekyll MCP Server 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 post data by various filters (keyword, category, tags) with no capability to create, modify, delete, or execute external operations. It has minimal blast radius if misused by an AI agent—worst case being excessive searches or information disclosure of already-public blog content.
From the tool's definition Tool performs search operations on blog content without modification. The description 'Search blog posts by query, category, or tags' and server context 'searches Jekyll blog content' indicate querying/retrieval only.
Attacks that exploit this kind of access
Search blog posts by query, category, or tags. It is categorised as a Read tool in the Jekyll MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jekyll MCP Server MCP server in PolicyLayer and add a rule for search_posts: 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 Jekyll MCP Server. Nothing to install.
search_posts 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_posts 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_posts. 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_posts is provided by the Jekyll MCP Server MCP server (jottinger/jekyll-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_posts is one line of Jekyll MCP Server'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 →