Create a new index with optional primary key
AI agents use create-index to create or update resources in Meilisearch MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meilisearch MCP Server environment.
The tool creates a new index in Meilisearch, which is a reversible operation (indices can be deleted). This is a Write action: it modifies the state of the search service by adding a new organizational structure.
From the tool's definition Tool name 'create-index' and description 'Create a new index with optional primary key' explicitly indicate creation of a new data structure/container.
Documented attack patterns abuse exactly the kind of access create-index gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meilisearch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-index:
{
"version": "1",
"default": "deny",
"tools": {
"create-index": {
"limits": [
{
"counter": "create-index_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Create a new index with optional primary key. It is categorised as a Write tool in the Meilisearch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meilisearch MCP Server 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 Meilisearch MCP Server. 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 Meilisearch MCP Server MCP server (meilisearch/meilisearch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meilisearch MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Meilisearch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.