Get blog post details by URL
AI agents call get_post_by_url to retrieve information from Hatena Blog 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 existing blog post content by URL without side effects. It is a straightforward read operation that queries and returns data. No data is created, modified, deleted, or executed. The low severity reflects minimal risk—misuse would only expose publicly available blog content.
From the tool's definition Tool name 'get_post_by_url' and description 'Get blog post details by URL' indicate data retrieval. Server description confirms the tool 'support[s] retrieving post details by URL' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get blog post details by URL. It is categorised as a Read tool in the Hatena Blog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hatena Blog MCP Server MCP server in PolicyLayer and add a rule for get_post_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 Hatena Blog MCP Server. Nothing to install.
get_post_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_post_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_post_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_post_by_url is provided by the Hatena Blog MCP Server MCP server (serima/hatena-blog-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 →