hn_story
Get details for a specific story by ID
This record as markdown: /tools/imprvhub-mcp-claude-hackernews/hn-story.md
What hn_story does on Hacker News MCP
AI agents call hn_story to retrieve information from Hacker News MCP 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 |
|---|---|---|---|
story_id | number | — | The ID of the story to fetch |
Parameters from the server's own tool schema.
Why hn_story is rated Low
This tool retrieves story details from Hacker News by querying an ID parameter. It has no side effects—it only fetches and returns data without creating, modifying, or deleting any information. This is a pure read operation with minimal security risk.
From the tool's definition Tool name 'hn_story' and description 'Get details for a specific story by ID' indicate a retrieval operation. No modification, deletion, or code execution capabilities are present.
Attacks that exploit this kind of access
The rule that runs hn_story safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hacker News MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hn_story, this is the rule to start with:
hn_story 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 Hacker News MCP, apply this rule, and every hn_story call is checked against it from then on.
Questions about hn_story
Get details for a specific story by ID. It is categorised as a Read tool in the Hacker News MCP MCP Server, which means it retrieves data without modifying state.
hn_story accepts 1 parameter: story_id. The full parameter table on this page comes from the server's own tool schema.
Register the Hacker News MCP server in PolicyLayer and add a rule for hn_story: 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 Hacker News MCP. Nothing to install.
hn_story 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 hn_story 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 hn_story. 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.
hn_story is provided by the Hacker News MCP server (imprvhub/mcp-claude-hackernews). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hacker News, and thousands of servers like it.
This server
Across the catalogue