AI agents call get_post to retrieve information from Blogger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves blog post data without modifying, deleting, or publishing anything. It is a straightforward query operation. The low severity reflects minimal blast radius — fetching a post cannot cause unintended harm even if the wrong post ID is supplied.
From the tool's definition Tool description states 'Fetch a single post' — a retrieval operation with no side effects. Confirmed by sibling tools on the server which include destructive operations (delete_post), write operations (create_post, update_post), and publish/revert actions,…
Attacks that exploit this kind of access
Fetch a single post. It is categorised as a Read tool in the Blogger MCP Server, which means it retrieves data without modifying state.
Register the Blogger MCP server in PolicyLayer and add a rule for 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 Blogger. Nothing to install.
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 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 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.
get_post is provided by the Blogger MCP server (mech12/blogger-mcp). 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 →