Search for blogs by title using the mock API.
AI agents call search_blogs to retrieve information from MCP Blog API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data matching a search criterion without side effects. Searching is a read-only operation that does not create, modify, delete, or execute external operations. The low severity reflects minimal blast radius—a misused search can only return unwanted information, not alter state or incur costs.
From the tool's definition Tool description states 'Search for blogs by title' with no mention of modification, deletion, or execution of arbitrary code. The sibling tools 'add_blog' (Write) and 'get_blogs' (Read) confirm this is a query operation.
Attacks that exploit this kind of access
Search for blogs by title using the mock API. It is categorised as a Read tool in the MCP Blog API MCP Server, which means it retrieves data without modifying state.
Register the MCP Blog API MCP server in PolicyLayer and add a rule for search_blogs: 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 Blog API. Nothing to install.
search_blogs 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_blogs 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_blogs. 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_blogs is provided by the MCP Blog API MCP server (tussanakorn/poc_mcp_protocol_using_fastmcp). 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 →