Low Risk

get_page

주어진 페이지 ID로 페이지를 조회합니다.

How to control get_page ↓

What get_page does on Wikidocs

AI agents call get_page 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_page needs a policy

This tool performs data retrieval without modifying, deleting, or executing operations. It simply queries and returns page content based on a page ID parameter. The blast radius of misuse is minimal—an agent could retrieve unauthorized pages if access controls are insufficient, but cannot modify or delete data.

From the tool's definition Tool name is 'get_page' and description translates to 'retrieves/queries a page by given page ID'. The verb 'get' and the retrieval-only operation confirm this is a read operation with no side effects.

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

How to control get_page

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

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

get_page 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_page

What does the get_page tool do? +

주어진 페이지 ID로 페이지를 조회합니다. 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_page? +

Register the Wikidocs MCP server in PolicyLayer and add a rule for get_page: 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_page? +

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

Can I rate-limit get_page? +

Yes. Add a rate_limit block to the get_page 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_page completely? +

Set action: deny in the PolicyLayer policy for get_page. 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_page? +

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