This record as markdown: /tools/io-github-portel-dev-ncp/bulk-operations.md
What bulk_operations does on Ncp
AI agents invoke bulk_operations to trigger actions in Ncp. 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 bulk_operations is rated High
Elasticsearch bulk operations encompass a range of actions including create, index, update, and delete across potentially large datasets. Since the tool can span Write, Destructive, and Execute categories, the most severe applicable is chosen. Bulk deletions or overwrites could be irreversible at scale, making this high severity.
From the tool's definition 'Perform bulk operations on Elasticsearch' — bulk operations in Elasticsearch can include indexing, updating, and deleting documents at scale
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_operations 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_operations, this is the rule to start with:
bulk_operations 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 Ncp, apply this rule, and every bulk_operations call is checked against it from then on.
Questions about bulk_operations
Perform bulk operations on Elasticsearch. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ncp MCP server in PolicyLayer and add a rule for bulk_operations: 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_operations 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 bulk_operations 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_operations. 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_operations 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