AI agents call search-blog to retrieve information from Kakao API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves blog search results from Daum's search service. It performs read-only operations with no data modification, deletion, code execution, or financial impact. The verb 'search' combined with the public nature of blog content retrieval confirms this is a Read operation with minimal risk.
From the tool's definition Tool name 'search-blog' and description '다음(Daum) 검색에서 블로그 글을 검색합니다' (Daum search to search blog posts) indicate a search/retrieval function with no side effects.
Documented attack patterns abuse exactly the kind of access search-blog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kakao API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search-blog:
{
"version": "1",
"default": "deny",
"tools": {
"search-blog": {}
}
}search-blog is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
다음(Daum) 검색에서 블로그 글을 검색합니다. It is categorised as a Read tool in the Kakao API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kakao API MCP Server MCP server in PolicyLayer and add a rule for search-blog: 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 Kakao API MCP Server. Nothing to install.
search-blog 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-blog 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-blog. 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-blog is provided by the Kakao API MCP Server MCP server (jeong-sik/kakao-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kakao API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Kakao API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.