get-keys · Meilisearch MCP Server MCP: Risk & Policy

WHAT IT DOES

What get-keys does on Meilisearch MCP Server

AI agents call get-keys to retrieve information from Meilisearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get-keys needs a policy

This tool retrieves and enumerates API keys from the Meilisearch instance. While it is fundamentally a Read operation (no side effects or data modification), the exposure of API keys themselves represents a moderate security risk, as an AI agent could potentially extract sensitive credentials for misuse.

From the tool's definition Tool name 'get-keys' with description 'List all API keys' indicates data retrieval with no modification.

Documented attack patterns abuse exactly the kind of access get-keys gives an agent:

POLICY

How to control get-keys

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 get-keys:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-keys": {}
  }
}

get-keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Meilisearch MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Meilisearch MCP Server tools

Destructive cancel-tasks Cancel pending or enqueued tasks Destructive delete-index Delete an existing index and all its documents Destructive delete-key Delete an existing API key Destructive delete-tasks Delete completed tasks Write add-documents Add or update documents in an index Write create-index Create a new index with optional primary key Write create-key Create new API key with specific permissions Write update-connection-settings Update URL and/or API key to connect to a different instance

All 23 Meilisearch MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-keys

What does the get-keys tool do? +

List all API keys. It is categorised as a Read tool in the Meilisearch MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-keys? +

Register the Meilisearch MCP Server MCP server in PolicyLayer and add a rule for get-keys: 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.

What risk level is get-keys? +

get-keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-keys? +

Yes. Add a rate_limit block to the get-keys 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.

How do I block get-keys completely? +

Set action: deny in the PolicyLayer policy for get-keys. 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.

What MCP server provides get-keys? +

get-keys 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.

Enforce policy on every Meilisearch MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

23 Meilisearch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.