algolia_search
Search an Algolia index for records matching a query.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/algolia-search.md
What algolia_search does on UnClick
AI agents call algolia_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number (0-indexed) |
index | string | Yes | Index name to search |
query | string | — | Search query text |
app_id | string | Yes | Algolia Application ID |
api_key | string | Yes | Algolia API Key (Search or Admin) |
filters | string | — | Algolia filter expression (e.g. category:electronics) |
hits_per_page | number | — | Results per page (default: 20) |
attributes_to_retrieve | array | — | Attributes to include in results |
Parameters from the server's own tool schema.
Why algolia_search is rated Low
This tool performs a query-based retrieval of records from an Algolia search index. The action is read-only with no side effects—it does not create, modify, delete, or execute code. The only potential risk is exposure of information in the index itself, which is inherent to any search capability and represents low severity.
From the tool's definition Tool name 'algolia_search' and description 'Search an Algolia index for records matching a query' indicate a search operation that retrieves data without modification.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs algolia_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For algolia_search, this is the rule to start with:
algolia_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every algolia_search call is checked against it from then on.
Questions about algolia_search
Search an Algolia index for records matching a query. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
algolia_search accepts 8 parameters: page, index, query, app_id, api_key, filters, hits_per_page, attributes_to_retrieve. Required: index, app_id, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for algolia_search: 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 UnClick. Nothing to install.
algolia_search 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 algolia_search 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 algolia_search. 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.
algolia_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue