Récupère les détails d\
AI agents call get_post to retrieve information from Blogger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing blog post data with no side effects. It is a read-only operation that returns post details. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—at worst, an AI agent might retrieve posts it shouldn't have access to, but no destructive or financial harm is possible.
From the tool's definition Tool name 'get_post' and context 'Récupère les détails' (French: 'Retrieves the details') indicate a data retrieval operation. The tool fetches post information from the Blogger API without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Récupère les détails d\. It is categorised as a Read tool in the Blogger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blogger MCP Server 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 MCP Server. 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 MCP server (niyonabil/blogger-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 →