Low Risk

get_cache_status

책 캐시 상태를 확인합니다. 어떤 책이 캐시되어 있는지, 언제 캐시되었는지 확인할 수 있습니다.

How to control get_cache_status ↓

What get_cache_status does on Wikidocs

AI agents call get_cache_status 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_cache_status needs a policy

This tool queries cache status information to view which books are cached and their timestamps. No side effects, modifications, or external operations are triggered. It is a pure information retrieval function, making it a Read operation with low severity since cache metadata exposure presents minimal security risk.

From the tool's definition Tool description (translated: 'Check book cache status. You can see which books are cached and when they were cached.') indicates the tool retrieves cache metadata about books without modifying, deleting, or executing operations.

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

How to control get_cache_status

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

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

get_cache_status 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_cache_status

What does the get_cache_status tool do? +

책 캐시 상태를 확인합니다. 어떤 책이 캐시되어 있는지, 언제 캐시되었는지 확인할 수 있습니다. 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_cache_status? +

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

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

Can I rate-limit get_cache_status? +

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

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

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