This record as markdown: /tools/0xcybin-jobs-mcp/search-hn-jobs.md
What search_hn_jobs does on Jobs
AI agents call search_hn_jobs to retrieve information from Jobs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_hn_jobs is rated Low
This tool retrieves or queries data from Hacker News job listings with no side effects, state changes, or destructive actions. It is a straightforward read operation consistent with other search tools on this server (search_upwork_jobs, search_github_jobs, search_remote_jobs). Low severity reflects minimal risk even if misused—an AI agent can only retrieve job data, which is already public.
From the tool's definition search_hn_jobs with description 'Search Hacker News' performs a query operation that retrieves job listings without modifying, deleting, or executing any code.
Attacks that exploit this kind of access
The rule that runs search_hn_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jobs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_hn_jobs, this is the rule to start with:
search_hn_jobs 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 Jobs, apply this rule, and every search_hn_jobs call is checked against it from then on.
Questions about search_hn_jobs
Search Hacker News. It is categorised as a Read tool in the Jobs MCP Server, which means it retrieves data without modifying state.
Register the Jobs MCP server in PolicyLayer and add a rule for search_hn_jobs: 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 Jobs. Nothing to install.
search_hn_jobs 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 search_hn_jobs 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 search_hn_jobs. 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.
search_hn_jobs is provided by the Jobs MCP server (0xcybin/jobs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jobs, and thousands of servers like it.
This server
Across the catalogue