AI agents call hn_story to retrieve information from Devfeed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries a single Hacker News story, which is a read-only operation with no data modification, deletion, code execution, or financial impact. The lowest severity is appropriate as fetching public discussion content poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'hn_story' and description 'Get an HN story' indicate data retrieval from Hacker News with no modification or side effects.
Attacks that exploit this kind of access
Get an HN story. It is categorised as a Read tool in the Devfeed MCP Server, which means it retrieves data without modifying state.
Register the Devfeed 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 Devfeed. 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 Devfeed MCP server (upgpt-ai/devfeed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →