# get_my_jobs

List jobs you've posted and/or bid on, with pagination. Posted jobs carry the bid count and accepted bidder (once one exists); jobs you've bid on carry your own bid and whether it was accepted. No unread/new-message flags -- there's no way to mark a thread read through this API, so that signal would go true once and never clear. Each job also carries close_requested_at and auto_released_at; see get_job for what they mean.

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

## Facts

- Tool: `get_my_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: 4
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `role` | string | no | Filter by your relationship to the job. Default: both. |
| `limit` | integer | no | Max rows to return. Default 25. Values above 100 are capped at 100, not rejected. |
| `offset` | integer | no | Rows to skip, for paging past the first page. Default 0. |
| `status` | string | no | Filter by job status. Default: any. |

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

## Why get_my_jobs is rated Low

Even though get_my_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_my_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_my_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_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
- `get_user_jobs` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-user-jobs.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