AI agents use add-documents 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.
This tool creates or modifies documents in a Meilisearch index. These changes are reversible (documents can be deleted or updated again), so it falls under Write rather than Destructive. The severity is medium because misuse could corrupt search data or add malicious content to the index, but the blast radius is limited to that index and the changes are not permanent.
From the tool's definition Tool name 'add-documents' and description 'Add or update documents in an index' clearly indicate reversible creation and modification of data in a search index.
Documented attack patterns abuse exactly the kind of access add-documents 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 add-documents:
{
"version": "1",
"default": "deny",
"tools": {
"add-documents": {
"limits": [
{
"counter": "add-documents_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-documents 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.
Add or update documents in an index. 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 add-documents: 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.
add-documents 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 add-documents 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 add-documents. 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.
add-documents 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.