This record as markdown: /tools/io-github-portel-dev-ncp/create-index.md
What create_index does on Ncp
AI agents use create_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 create_index is rated Medium
Creating an index is a reversible Write operation that establishes a new searchable data container. While it consumes resources and affects system state, it does not delete data, execute arbitrary code, or cause irreversible damage.
From the tool's definition Tool name is 'create_index' and description states 'Create new Elasticsearch index' — this creates a new data structure in Elasticsearch without modifying or deleting existing data.
Attacks that exploit this kind of access
The rule that runs create_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 create_index, this is the rule to start with:
create_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 create_index call is checked against it from then on.
Questions about create_index
Create new Elasticsearch index. 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 create_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.
create_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 create_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 create_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.
create_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