post-indexer-by-index-name-rebuild

WHAT IT DOES

What post-indexer-by-index-name-rebuild does on Mcp Dev

AI agents invoke post-indexer-by-index-name-rebuild to trigger actions in Mcp Dev. 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 post-indexer-by-index-name-rebuild needs a policy

Rebuilding a search index is an execute-category action: it triggers a significant external operation (full reindex) that can consume substantial resources and time. It is not purely destructive (the index is rebuilt, not deleted permanently), but it is more than a simple write since it triggers a system-level process.

From the tool's definition 'Rebuilds a specific index by name' and 'will trigger a full rebuild of the index' — this triggers an external long-running operation that rewrites the search index entirely

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

post-indexer-by-index-name-rebuild Rate-limited

post-indexer-by-index-name-rebuild 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": {
    "post-indexer-by-index-name-rebuild": {
      "limits": [
        {
          "counter": "post-indexer-by-index-name-rebuild_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 Mcp Dev, so you can run agents against it safely.

FAQ

Questions about post-indexer-by-index-name-rebuild

What does the post-indexer-by-index-name-rebuild tool do? +

Rebuilds a specific index by name. This operation will trigger a full rebuild of the index, which may take some time depending on the amount of content. Use this only when asked to by the user. It is categorised as a Execute tool in the Mcp Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on post-indexer-by-index-name-rebuild? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for post-indexer-by-index-name-rebuild: 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 Mcp Dev. Nothing to install.

What risk level is post-indexer-by-index-name-rebuild? +

post-indexer-by-index-name-rebuild is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit post-indexer-by-index-name-rebuild? +

Yes. Add a rate_limit block to the post-indexer-by-index-name-rebuild 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 post-indexer-by-index-name-rebuild completely? +

Set action: deny in the PolicyLayer policy for post-indexer-by-index-name-rebuild. 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 post-indexer-by-index-name-rebuild? +

post-indexer-by-index-name-rebuild is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.