AI agents call algolia_browse_index to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
index | string | Yes | Index name |
app_id | string | Yes | Algolia Application ID |
cursor | string | — | Pagination cursor from previous response |
api_key | string | Yes | Algolia Admin API Key |
filters | string | — | Filter expression |
hits_per_page | number | — | Records per page |
attributes_to_retrieve | array | — | Attributes to include |
Parameters from the server's own tool schema.
The tool retrieves and iterates through existing records in an Algolia search index. This is a query/retrieval operation with no side effects—it does not create, modify, delete, or execute anything. Severity is low because browsing indexed data poses minimal risk unless the index contains highly sensitive information, but the tool itself is fundamentally a read operation.
From the tool's definition Tool name and description indicate browsing and retrieval: 'Browse all records' and 'paginated cursor-based' are read-only operations with no modification, deletion, or execution capabilities.
Risk signalsHandles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Browse all records in an Algolia index (paginated cursor-based). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
algolia_browse_index accepts 7 parameters: index, app_id, cursor, 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_browse_index: 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_browse_index 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_browse_index 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_browse_index. 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_browse_index 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →