rebuild_search_index
Rebuild Context Store FTS index for documents, facts, and runbooks.
This record as markdown: /tools/mcp-control-plane/rebuild-search-index.md
What rebuild_search_index does on Mcp Control Plane
AI agents invoke rebuild_search_index to trigger actions in Mcp Control Plane. 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 rebuild_search_index is rated High
Rebuilding a full-text search (FTS) index is an active operation that reprocesses existing data and regenerates internal index structures. It is not a simple read, nor does it delete data, but it executes a potentially resource-intensive background process that modifies internal state (the index). Misuse could cause performance degradation or temporary unavailability of search functionality, hence medium severity.
From the tool's definition 'Rebuild Context Store FTS index' — triggers an index rebuild operation on stored documents, facts, and runbooks
Attacks that exploit this kind of access
The rule that runs rebuild_search_index safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rebuild_search_index, this is the rule to start with:
rebuild_search_index 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every rebuild_search_index call is checked against it from then on.
Questions about rebuild_search_index
Rebuild Context Store FTS index for documents, facts, and runbooks. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for rebuild_search_index: 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 Control Plane. Nothing to install.
rebuild_search_index is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rebuild_search_index 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.
Set action: deny in the PolicyLayer policy for rebuild_search_index. 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.
rebuild_search_index is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue