hnalgolia.search.comments
Search HackerNews comments by keyword — retrieves community opinions, technical insights, and discussions across the full HN history. Each result includes comment text (HTML-stripped), parent story context (title + URL), author, and direct HN link. No auth required. Data: Hacker News (CC BY 3.0).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hnalgolia.search.comments.md
What hnalgolia.search.comments does on Apibase
AI agents call hnalgolia.search.comments to retrieve information from Apibase 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 | integer | — | Zero-based page index for pagination (default 0). |
limit | integer | — | Number of comments to return (1–30, default 10). |
query | string | Yes | Search query to find comments across HackerNews history. Returns comment text, story context (title + URL), author, and direct HN link. Useful for finding commu |
Parameters from the server's own tool schema.
Why hnalgolia.search.comments is rated Low
Queries public Hacker News data without modifying, executing, or affecting external systems.
From the tool's definition Search HackerNews comments by keyword — retrieves community opinions, technical insights
Attacks that exploit this kind of access
The rule that runs hnalgolia.search.comments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hnalgolia.search.comments, this is the rule to start with:
hnalgolia.search.comments 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 Apibase, apply this rule, and every hnalgolia.search.comments call is checked against it from then on.
Questions about hnalgolia.search.comments
Search HackerNews comments by keyword — retrieves community opinions, technical insights, and discussions across the full HN history. Each result includes comment text (HTML-stripped), parent story context (title + URL), author, and direct HN link. No auth required. Data: Hacker News (CC BY 3.0). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
hnalgolia.search.comments accepts 3 parameters: page, limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for hnalgolia.search.comments: 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 Apibase. Nothing to install.
hnalgolia.search.comments 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 hnalgolia.search.comments 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 hnalgolia.search.comments. 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.
hnalgolia.search.comments is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue