This record as markdown: /tools/io-github-portel-dev-ncp/bulk-index.md
What bulk_index does on Ncp
AI agents use bulk_index to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why bulk_index is rated Medium
Indexing is a write operation that creates or modifies data (index structures) but is reversible—indexes can be rebuilt or deleted without data loss. The 'bulk' aspect increases the blast radius to medium severity, as a misconfigured bulk operation could index large quantities of unintended documents or overwrite existing indexes.
From the tool's definition Tool name is 'bulk_index' with description 'Bulk index documents'. Indexing modifies data structures (creates or updates indexes) in a reversible manner.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_index safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_index, this is the rule to start with:
bulk_index 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every bulk_index call is checked against it from then on.
Questions about bulk_index
Bulk index documents. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for bulk_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 Ncp. Nothing to install.
bulk_index 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 bulk_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 bulk_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.
bulk_index is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue