# search_remote_jobs

Search remote jobs from RemoteOK. Returns title, company, tags, salary, URL.

Agent View of the PolicyLayer registry record for `search_remote_jobs`. HTML page: https://policylayer.com/tools/0xcybin-jobs-mcp/search-remote-jobs

## Facts

- Tool: `search_remote_jobs`
- 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": "search_remote_jobs",
    "arguments": {}
  }
}
```

## Why search_remote_jobs is rated Low

This tool performs a read-only query operation against a job board API. It retrieves publicly available job listings and returns structured data with no side effects, state changes, or capability to execute code or trigger external operations. The search functionality is a standard information retrieval pattern with no destructive, financial, or execution risks.

From the tool's own definition: "Tool searches and returns job data (title, company, tags, salary, URL) without modifying, deleting, or executing any actions. Description explicitly indicates retrieval: 'Search remote jobs from RemoteOK. Returns title, company, tags, salary, URL.'"

## Use case

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

## 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": {
    "search_remote_jobs": {}
  }
}
```

## Other tools on Jobs (7)

- `job_scan` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/job-scan.md
- `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_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
