Index or re-index all documentation for improved search
AI agents use index_docs to create or update resources in Dedalus MCP Documentation Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dedalus MCP Documentation Server environment.
Indexing rebuilds or overwrites the search index data structure. This is a Write operation (reversible modification of the index store) with no irreversible deletion of source documents. Misuse could cause search disruption or resource exhaustion due to re-indexing costs, hence medium severity.
From the tool's definition 'Index or re-index all documentation for improved search' — creates or updates a search index from existing documentation files
Attacks that exploit this kind of access
Index or re-index all documentation for improved search. It is categorised as a Write tool in the Dedalus MCP Documentation Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dedalus MCP Documentation Server MCP server in PolicyLayer and add a rule for index_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 Dedalus MCP Documentation Server. Nothing to install.
index_docs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the index_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.
Set action: deny in the PolicyLayer policy for index_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.
index_docs is provided by the Dedalus MCP Documentation Server MCP server (kitan23/python_mcp_server_example_2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →