View current Meilisearch connection URL and API key status
AI agents call get-connection-settings 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.
This tool retrieves connection metadata (URL and API key status) with no side effects. It is a pure information-gathering operation that does not create, modify, delete, or execute anything. The severity is low because viewing connection settings has minimal blast radius—it cannot be misused to cause substantial harm, though the API key status could be sensitive information that an agent should not expose.
From the tool's definition Tool name 'get-connection-settings' and description 'View current Meilisearch connection URL and API key status' indicate a read-only operation that retrieves configuration information without modifying, executing, or deleting data.
Documented attack patterns abuse exactly the kind of access get-connection-settings 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 get-connection-settings:
{
"version": "1",
"default": "deny",
"tools": {
"get-connection-settings": {}
}
} get-connection-settings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
View current Meilisearch connection URL and API key status. It is categorised as a Read tool in the Meilisearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meilisearch MCP Server MCP server in PolicyLayer and add a rule for get-connection-settings: 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.
get-connection-settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-connection-settings 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 get-connection-settings. 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.
get-connection-settings 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.