This record as markdown: /tools/creativelead-unclick/hn-new-stories.md
What hn_new_stories does on UnClick
AI agents call hn_new_stories to retrieve information from UnClick 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 | number | — |
Parameters from the server's own tool schema.
Why hn_new_stories is rated Low
This tool retrieves publicly available stories from Hacker News. It is a pure read/fetch operation with no side effects, no data modification, and no destructive or financial implications. Misuse potential is minimal.
From the tool's definition Get the newest stories from Hacker News
Attacks that exploit this kind of access
The rule that runs hn_new_stories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hn_new_stories, this is the rule to start with:
hn_new_stories 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 UnClick, apply this rule, and every hn_new_stories call is checked against it from then on.
Questions about hn_new_stories
Get the newest stories from Hacker News. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hn_new_stories accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for hn_new_stories: 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 UnClick. Nothing to install.
hn_new_stories 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_new_stories 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_new_stories. 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_new_stories is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue