hackernews.stories.new
Fetch the most recently submitted stories from Hacker News — up to 20 posts sorted by submission time (newest first). Useful for monitoring breaking tech news and community discussion before posts gain front-page visibility. Returns title, URL, author, score, and comment count. No auth required. ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hackernews.stories.new.md
What hackernews.stories.new does on Apibase
AI agents call hackernews.stories.new 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 newest stories to return (1–20, default 10). Sorted by submission time, most recent first. |
Parameters from the server's own tool schema.
Why hackernews.stories.new is rated Low
Retrieves public news data with no side effects or access control implications.
From the tool's definition Fetch the most recently submitted stories from Hacker News
Attacks that exploit this kind of access
The rule that runs hackernews.stories.new 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.new, this is the rule to start with:
hackernews.stories.new 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.new call is checked against it from then on.
Questions about hackernews.stories.new
Fetch the most recently submitted stories from Hacker News — up to 20 posts sorted by submission time (newest first). Useful for monitoring breaking tech news and community discussion before posts gain front-page visibility. Returns 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.new 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.new: 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.new 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.new 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.new. 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.new 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