AI agents call hn_who_is_hiring 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 performs a read-only search operation to find hiring threads on Hacker News. It retrieves and presents information without side effects, aligning with the Read category definition. The severity is low as misuse would only affect information retrieval quality, with no ability to modify, delete, or execute operations.
From the tool's definition Tool name 'hn_who_is_hiring' and description 'Search the latest HN' indicate a search/query operation that retrieves hiring-related content from Hacker News without modifying data or executing external operations.
Attacks that exploit this kind of access
Search the latest HN. 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_who_is_hiring: 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_who_is_hiring 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_who_is_hiring 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_who_is_hiring. 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_who_is_hiring 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 →