AI agents call blog_get_post to retrieve information from Mcp Blog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
blog_get_post performs a retrieval operation only—it fetches and returns blog post data without modifying, deleting, or executing side effects. This is a classic Read category operation. The editing workflow context confirms it is the fetch step prior to write operations handled by other tools. Severity is low because reading blog content poses minimal risk.
From the tool's definition Tool description states it 'reads out the article from S3' (S3 から読み出し) and 'returns the Markdown body and frontmatter' (Markdown 本体と frontmatter を返す). It is used in an edit workflow for retrieval (取得→修正) before modification by blog_publish_post.
Attacks that exploit this kind of access
指定したスラグの記事を S3 から読み出し、Markdown 本体と frontmatter を返す。編集ワークフロー (取得→修正→blog_publish_post で上書き) で使う。. It is categorised as a Read tool in the Mcp Blog MCP Server, which means it retrieves data without modifying state.
Register the Mcp Blog MCP server in PolicyLayer and add a rule for blog_get_post: 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. Nothing to install.
blog_get_post 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 blog_get_post 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 blog_get_post. 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.
blog_get_post is provided by the Mcp Blog MCP server (masatoshisano/mcp-blog). 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 →