获取博主内容详情，包含完整原文（post_media_text）。需要 topic.blogger.read scope。
AI agents call get_blogger_content_detail to retrieve information from GetNote 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 and queries data about blogger content without side effects or ability to modify state. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The 'get' prefix and read scope confirm retrieval-only semantics. Low severity because misuse would only expose existing data, with limited blast radius.
From the tool's definition get_blogger_content_detail retrieves blogger content details including full text (post_media_text). The description explicitly requires 'topic.blogger.read' scope, indicating read-only access.
Documented attack patterns abuse exactly the kind of access get_blogger_content_detail gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GetNote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_blogger_content_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_blogger_content_detail": {}
}
}get_blogger_content_detail is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取博主内容详情，包含完整原文（post_media_text）。需要 topic.blogger.read scope。. It is categorised as a Read tool in the GetNote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GetNote MCP Server MCP server in PolicyLayer and add a rule for get_blogger_content_detail: 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 GetNote MCP Server. Nothing to install.
get_blogger_content_detail 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_blogger_content_detail 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_blogger_content_detail. 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_blogger_content_detail is provided by the GetNote MCP Server MCP server (iswalle/getnote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GetNote MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 GetNote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.