# get_company_jobs

列出「某一家指定公司」在 104 上在徵的職缺（職稱、地區、薪資、學經歷要求、網址），可分頁。公司用 find_company 回傳的 companyId，或 search_jobs / get_job_detail 回傳的 companyUrl。

Agent View of the PolicyLayer registry record for `get_company_jobs`. HTML page: https://policylayer.com/tools/104-mcp-server/get-company-jobs

## Facts

- Tool: `get_company_jobs`
- Server: 104 (`a7512cs/104-mcp-server`) — https://policylayer.com/tools/104-mcp-server.md
- Homepage: https://github.com/a7512cs/104-mcp-server
- 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": "get_company_jobs",
    "arguments": {}
  }
}
```

## Why get_company_jobs is rated Low

Even though get_company_jobs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_company_jobs to retrieve information from 104 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 104:

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

## Other tools on 104 (4)

- `find_company` — Read — https://policylayer.com/tools/104-mcp-server/find-company.md
- `get_apply_analysis` — Read — https://policylayer.com/tools/104-mcp-server/get-apply-analysis.md
- `get_job_detail` — Read — https://policylayer.com/tools/104-mcp-server/get-job-detail.md
- `search_jobs` — Read — https://policylayer.com/tools/104-mcp-server/search-jobs.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=104-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/104-mcp-server