hnalgolia.item.details
Fetch full details for any HackerNews item by integer ID using the Algolia API — returns type, title, URL, author, score, body text, creation time, and the top 5 child comments. Works for stories, Ask HN, Show HN, comments, jobs, and polls. No auth required. Data: Hacker News (CC BY 3.0).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hnalgolia.item.details.md
What hnalgolia.item.details does on Apibase
AI agents call hnalgolia.item.details 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 |
|---|---|---|---|
id | integer | Yes | HackerNews item ID (positive integer). Works for stories, comments, Ask HN, Show HN, jobs, and polls. Example: 48713832. |
Parameters from the server's own tool schema.
Why hnalgolia.item.details is rated Low
Tool retrieves public HackerNews data with no side effects or authentication requirements.
From the tool's definition Fetch full details for any HackerNews item by integer ID using the Algolia API
Attacks that exploit this kind of access
The rule that runs hnalgolia.item.details 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.item.details, this is the rule to start with:
hnalgolia.item.details 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.item.details call is checked against it from then on.
Questions about hnalgolia.item.details
Fetch full details for any HackerNews item by integer ID using the Algolia API — returns type, title, URL, author, score, body text, creation time, and the top 5 child comments. Works for stories, Ask HN, Show HN, comments, jobs, and polls. 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.item.details accepts 1 parameter: id. Required: id. 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.item.details: 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.item.details 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.item.details 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.item.details. 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.item.details 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