hackernews.stories.best
Fetch the best-rated stories from Hacker News — high-quality posts selected by the HN "best" feed algorithm which balances score, engagement, and editorial quality. Up to 20 stories with title, URL, author, score, and comment count. No auth required. Data: Hacker News (CC BY 3.0).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hackernews.stories.best.md
What hackernews.stories.best does on Apibase
AI agents call hackernews.stories.best 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 |
|---|---|---|---|
limit | integer | — | Number of best stories to return (1–20, default 10). HackerNews "best" feed: high-quality posts with strong upvotes and engagement. |
Parameters from the server's own tool schema.
Why hackernews.stories.best is rated Low
Retrieves publicly available Hacker News data without side effects or risk.
From the tool's definition Fetch the best-rated stories from Hacker News with title, URL, author, score, comment count.
Attacks that exploit this kind of access
The rule that runs hackernews.stories.best 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 hackernews.stories.best, this is the rule to start with:
hackernews.stories.best 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 hackernews.stories.best call is checked against it from then on.
Questions about hackernews.stories.best
Fetch the best-rated stories from Hacker News — high-quality posts selected by the HN "best" feed algorithm which balances score, engagement, and editorial quality. Up to 20 stories with title, URL, author, score, and comment count. 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.
hackernews.stories.best accepts 1 parameter: limit. 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 hackernews.stories.best: 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.
hackernews.stories.best 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 hackernews.stories.best 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 hackernews.stories.best. 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.
hackernews.stories.best 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