refresh_all_docs · OmniDocs MCP: Risk & Policy

WHAT IT DOES

What refresh_all_docs does on OmniDocs MCP

AI agents use refresh_all_docs to create or update resources in OmniDocs MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniDocs MCP environment.

WHY IT NEEDS A POLICY

Why refresh_all_docs needs a policy

This tool overwrites/updates cached documentation for all tracked libraries. It's a bulk write operation that modifies stored cache data. While not destructive in the sense of permanent data loss (it refreshes rather than deletes), it does overwrite existing cached content for all libraries simultaneously, which could disrupt ongoing operations or introduce unexpected changes at scale.

From the tool's definition Force refresh cached docs for all tracked libraries

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_all_docs Rate-limited

refresh_all_docs stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_all_docs": {
      "limits": [
        {
          "counter": "refresh_all_docs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OmniDocs MCP, so you can run agents against it safely.

FAQ

Questions about refresh_all_docs

What does the refresh_all_docs tool do? +

Force refresh cached docs for all tracked libraries. It is categorised as a Write tool in the OmniDocs MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on refresh_all_docs? +

Register the OmniDocs MCP server in PolicyLayer and add a rule for refresh_all_docs: 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 OmniDocs MCP. Nothing to install.

What risk level is refresh_all_docs? +

refresh_all_docs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit refresh_all_docs? +

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

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

refresh_all_docs is provided by the OmniDocs MCP server (yogesh-g-3468/omnidocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.