hackernews_stories_job
Fetch current Hacker News job postings Fetch current Hacker News job postings. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_job
This record as markdown: /tools/com-replynodes-mcp/hackernews-stories-job.md
What hackernews_stories_job does on ReplyNodes
AI agents call hackernews_stories_job to retrieve information from ReplyNodes 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 |
|---|---|---|---|
page | integer | — | Result page. |
limit | integer | — | Maximum number of results; values outside 1..100 are rejected. |
Parameters from the server's own tool schema.
Why hackernews_stories_job is rated Low
Tool retrieves public job posting data from Hacker News with no side effects or state changes.
From the tool's definition Fetch current Hacker News job postings; no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs hackernews_stories_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hackernews_stories_job, this is the rule to start with:
hackernews_stories_job 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 ReplyNodes, apply this rule, and every hackernews_stories_job call is checked against it from then on.
Questions about hackernews_stories_job
Fetch current Hacker News job postings Fetch current Hacker News job postings. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_job. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
hackernews_stories_job accepts 2 parameters: page, limit. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for hackernews_stories_job: 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 ReplyNodes. Nothing to install.
hackernews_stories_job 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_job 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_job. 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_job is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue