AI agents call get_blog_by_url 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.
This tool performs a straightforward data retrieval operation—resolving a Blog ID from a URL. It does not create, modify, delete, or execute external actions. It is purely informational, making it a Read category tool with low severity, as misuse would only expose publicly accessible blog identifiers.
From the tool's definition Tool name 'get_blog_by_url' and description 'Resolve a Blog ID from a blog URL' indicate a lookup/query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Resolve a Blog ID from a blog URL (e.g. https://xxx.blogspot.com). 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_blog_by_url: 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_blog_by_url 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_blog_by_url 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_blog_by_url. 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_blog_by_url 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 →