reindex_documents · Confluence Knowledge Base MCP Server MCP

WHAT IT DOES

What reindex_documents does on Confluence Knowledge Base MCP Server

AI agents invoke reindex_documents to trigger actions in Confluence Knowledge Base MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why reindex_documents needs a policy

This tool triggers a bulk re-processing operation (loading and re-indexing all documentation files), which is an active execution of a pipeline rather than a simple read or write. It modifies the search index state and re-ingests all documents, which could have significant side effects such as temporarily disrupting search availability, overwriting existing index data, or consuming substantial resources.

From the tool's definition Re-load and re-index all local documentation files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reindex_documents Rate-limited

reindex_documents stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reindex_documents": {
      "limits": [
        {
          "counter": "reindex_documents_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about reindex_documents

What does the reindex_documents tool do? +

Re-load and re-index all local documentation files. It is categorised as a Execute tool in the Confluence Knowledge Base MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reindex_documents? +

Register the Confluence Knowledge Base MCP Server MCP server in PolicyLayer and add a rule for reindex_documents: 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 Confluence Knowledge Base MCP Server. Nothing to install.

What risk level is reindex_documents? +

reindex_documents is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reindex_documents? +

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

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

reindex_documents is provided by the Confluence Knowledge Base MCP Server MCP server (marcciosilva/confluence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.