AI agents call get_blog_profile to retrieve information from Wikidocs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation (get/read) with no side effects. It fetches profile information without creating, modifying, deleting, executing code, or affecting financial data. The low severity reflects the minimal blast radius if misused—an agent could retrieve profile information it shouldn't access, but cannot cause data loss or perform unauthorized actions through this tool alone.
From the tool's definition Tool name 'get_blog_profile' and description '블로그 프로필 정보를 조회합니다' (translates to 'Retrieves blog profile information') indicate a read-only query operation that retrieves existing profile data without modification.
Documented attack patterns abuse exactly the kind of access get_blog_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wikidocs, and nothing reaches the server without passing your rules. This is the rule we recommend for get_blog_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_blog_profile": {}
}
}get_blog_profile 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.
블로그 프로필 정보를 조회합니다. It is categorised as a Read tool in the Wikidocs MCP Server, which means it retrieves data without modifying state.
Register the Wikidocs MCP server in PolicyLayer and add a rule for get_blog_profile: 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 Wikidocs. Nothing to install.
get_blog_profile 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_profile 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_profile. 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_profile is provided by the Wikidocs MCP server (ychoi-kr/wikidocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wikidocs, 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.
17 Wikidocs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.