Lấy danh sách bài viết blog. Có thể filter theo status (draft/published), author, tag
AI agents call list_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 retrieves and queries existing blog post data. It supports filtering but does not create, modify, delete, or execute any side effects. It is a straightforward Read operation with minimal security risk—worst case, an AI agent might retrieve more blog posts than intended, which is low severity.
From the tool's definition Tool retrieves a list of blog posts with optional filtering by status, author, and tag. The description 'Lấy danh sách bài viết blog' (Get list of blog posts) and filter options indicate a read-only query operation with no modification or deletion of data.
Attacks that exploit this kind of access
Lấy danh sách bài viết blog. Có thể filter theo status (draft/published), author, tag. 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 list_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.
list_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 list_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 list_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.
list_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 →