Low Risk

get_blog_list

블로그 포스트 목록을 페이지별로 조회합니다. page 번호를 지정할 수 있습니다 (기본값: 1).

How to control get_blog_list ↓

What get_blog_list does on Wikidocs

AI agents call get_blog_list 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.

Low Risk

Why get_blog_list needs a policy

This tool performs a retrieval operation that queries and returns paginated blog post data. It has no capability to modify, delete, or execute operations. The paging parameter does not change its classification as a read operation. Blast radius is minimal since misuse would only retrieve accessible blog data without causing harm.

From the tool's definition Tool description translates to 'Retrieves blog post list by page. You can specify page number (default: 1).' The verb '조회합니다' (retrieves/queries) and the function of listing/paging blog posts indicates a read-only operation with no data modification or side…

Documented attack patterns abuse exactly the kind of access get_blog_list gives an agent:

How to control get_blog_list

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_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_blog_list": {}
  }
}

get_blog_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Wikidocs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_blog_list

What does the get_blog_list tool do? +

블로그 포스트 목록을 페이지별로 조회합니다. page 번호를 지정할 수 있습니다 (기본값: 1). It is categorised as a Read tool in the Wikidocs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_blog_list? +

Register the Wikidocs MCP server in PolicyLayer and add a rule for get_blog_list: 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.

What risk level is get_blog_list? +

get_blog_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_blog_list? +

Yes. Add a rate_limit block to the get_blog_list 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.

How do I block get_blog_list completely? +

Set action: deny in the PolicyLayer policy for get_blog_list. 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.

What MCP server provides get_blog_list? +

get_blog_list 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.

Enforce policy on every Wikidocs tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.