# job_scan

Scan multiple job sources at once for MCP, AI, TypeScript, and Discord jobs. Returns results from Upwork, RemoteOK, and HN. Use this for a daily job check.

Agent View of the PolicyLayer registry record for `job_scan`. HTML page: https://policylayer.com/tools/0xcybin-jobs-mcp/job-scan

## Facts

- Tool: `job_scan`
- Server: Jobs (`0xcybin/jobs-mcp`) — https://policylayer.com/tools/0xcybin-jobs-mcp.md
- Homepage: https://github.com/0xCybin/jobs-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "job_scan",
    "arguments": {}
  }
}
```

## Why job_scan is rated Low

job_scan performs read-only queries across multiple job platforms and aggregates the results. The tool searches and retrieves job listing data without creating, modifying, deleting, or executing anything. It is analogous to a search or list operation. The blast radius of misuse is minimal—an agent could at worst retrieve job listings repeatedly or return irrelevant results, but cannot harm systems or data.

From the tool's own definition: "Tool description states it 'Scan multiple job sources at once' and 'Returns results from Upwork, RemoteOK, and HN' — purely retrieval operations with no modification, deletion, execution, or financial side effects."

## Use case

AI agents call job_scan 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Jobs:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "job_scan": {}
  }
}
```

## Other tools on Jobs (7)

- `my_profile` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/my-profile.md
- `search_arbeitnow_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-arbeitnow-jobs.md
- `search_github_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-github-jobs.md
- `search_hn_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-hn-jobs.md
- `search_remote_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-remote-jobs.md
- `search_upwork_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-upwork-jobs.md
- `draft_proposal` — Write — https://policylayer.com/tools/0xcybin-jobs-mcp/draft-proposal.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xcybin-jobs-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xcybin-jobs-mcp