Tìm kiếm bài viết theo từ khóa trong tiêu đề và nội dung
AI agents call search_posts to retrieve information from MCP Blog Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only searches and retrieves blog posts matching keywords. It has no side effects—it does not create, modify, delete, execute code, or move money. Search is a canonical Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'search_posts' and description 'Tìm kiếm bài viết theo từ khóa trong tiêu đề và nội dung' (Search posts by keywords in title and content) indicate a query/search operation that retrieves data without modification.
Attacks that exploit this kind of access
Tìm kiếm bài viết theo từ khóa trong tiêu đề và nội dung. It is categorised as a Read tool in the MCP Blog Demo MCP Server, which means it retrieves data without modifying state.
Register the MCP Blog Demo 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 MCP Blog Demo. 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 MCP Blog Demo MCP server (trungls1706/mcp-server). 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 →