hnalgolia.search.recent
Full-text search over HackerNews history ranked by submission date (newest first) — ideal for finding the latest community discussions on any topic. Returns title, URL, author, score, and comment count. Supports filtering by type (story/ask/show/job/poll). No auth required. Data: Hacker News (CC ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hnalgolia.search.recent.md
What hnalgolia.search.recent does on Apibase
AI agents call hnalgolia.search.recent 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). |
type | string | — | Content type filter. "story" = submitted links; "ask" = Ask HN; "show" = Show HN; "job" = job listings. Default: story. |
limit | integer | — | Number of results to return (1–30, default 10). |
query | string | Yes | Full-text search query sorted by submission date (newest first). Ideal for finding the latest HN discussions on a topic. |
Parameters from the server's own tool schema.
Why hnalgolia.search.recent is rated Low
Tool queries publicly available HackerNews data without modification, authentication, or side effects.
From the tool's definition Full-text search over HackerNews history, returns title, URL, author, score, comment count
Attacks that exploit this kind of access
The rule that runs hnalgolia.search.recent 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.recent, this is the rule to start with:
hnalgolia.search.recent 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.recent call is checked against it from then on.
Questions about hnalgolia.search.recent
Full-text search over HackerNews history ranked by submission date (newest first) — ideal for finding the latest community discussions on any topic. Returns title, URL, author, score, and comment count. Supports filtering by type (story/ask/show/job/poll). 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.recent accepts 4 parameters: page, type, 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.recent: 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.recent 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.recent 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.recent. 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.recent 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