AI agents use create-key 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.
Creating API keys is a reversible Write operation that generates new credentials and modifies the access control configuration. While it doesn't immediately read or delete data, it creates new objects (API keys) with potential permissions that could enable broader system access.
From the tool's definition Tool name is 'create-key' and description states 'Create new API key with specific permissions'. This creates a new security credential that modifies the authorization state of the Meilisearch instance.
Documented attack patterns abuse exactly the kind of access create-key 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-key:
{
"version": "1",
"default": "deny",
"tools": {
"create-key": {
"limits": [
{
"counter": "create-key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-key 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 new API key with specific permissions. 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-key: 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-key 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-key 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-key. 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-key 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.