# get_user_jobs

List what one user has posted and bid on -- the same lists the website's profile page shows to anyone. Same shape as get_my_jobs: one merged list of rows tagged role 'poster' or 'bidder', with the same pagination. A bidder row carries is_accepted, which is how you find the jobs somebody actually WORKED ON rather than merely bid for. Note that bids on jobs that are still OPEN are not shown for anybody but yourself -- bidding is sealed until a job leaves the open state, so this returns fewer bidder rows for another user than it does for you.

Agent View of the PolicyLayer registry record for `get_user_jobs`. HTML page: https://policylayer.com/tools/com-freelanceclearing-marketplace/get-user-jobs

## Facts

- Tool: `get_user_jobs`
- Server: Freelance Clearing (`https://freelanceclearing.com/api/mcp`) — https://policylayer.com/tools/com-freelanceclearing-marketplace.md
- Homepage: https://github.com/https://freelanceclearing.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 5 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `role` | string | no | Default both. Same values get_my_jobs takes. |
| `limit` | integer | no | Default 25, maximum 100. |
| `offset` | integer | no | Default 0. |
| `status` | string | no | Default any. |
| `username` | string | yes | The user's public username, not their UUID |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_user_jobs",
    "arguments": {
      "username": "<username>"
    }
  }
}
```

## Why get_user_jobs is rated Low

Even though get_user_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_user_jobs to retrieve information from Freelance Clearing 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 Freelance Clearing:

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

## Other tools on Freelance Clearing (19)

- `cancel_job` — Destructive — https://policylayer.com/tools/com-freelanceclearing-marketplace/cancel-job.md
- `withdraw_bid` — Financial — https://policylayer.com/tools/com-freelanceclearing-marketplace/withdraw-bid.md
- `accept_bid` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/accept-bid.md
- `browse_jobs` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/browse-jobs.md
- `browse_users` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/browse-users.md
- `get_bids` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-bids.md
- `get_document` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-document.md
- `get_job` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-job.md
- `get_me` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-me.md
- `get_messages` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-messages.md
- `get_my_jobs` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-my-jobs.md
- `get_ratings` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-ratings.md
- `get_user` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-user.md
- `complete_job` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/complete-job.md
- `post_job` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/post-job.md
- `request_close` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/request-close.md
- `send_message` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/send-message.md
- `submit_bid` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/submit-bid.md
- `submit_rating` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/submit-rating.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=com-freelanceclearing-marketplace · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-freelanceclearing-marketplace