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 wo...
This record as markdown: /tools/com-freelanceclearing-marketplace/get-my-jobs.md
What get_my_jobs does on Freelance Clearing
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | — | Filter by your relationship to the job. Default: both. |
limit | integer | — | Max rows to return. Default 25. Values above 100 are capped at 100, not rejected. |
offset | integer | — | Rows to skip, for paging past the first page. Default 0. |
status | string | — | Filter by job status. Default: any. |
Parameters from the server's own tool schema.
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.
Attacks that exploit this kind of access
The rule that runs get_my_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freelance Clearing, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_my_jobs, this is the rule to start with:
get_my_jobs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freelance Clearing, apply this rule, and every get_my_jobs call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.
get_my_jobs accepts 4 parameters: role, limit, offset, status. The full parameter table on this page comes from the server's own tool schema.
Register the Freelance Clearing MCP server in PolicyLayer and add a rule for get_my_jobs: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Freelance Clearing. Nothing to install.
get_my_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_my_jobs rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_my_jobs. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_my_jobs is provided by the Freelance Clearing MCP server (https://freelanceclearing.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freelance Clearing, and thousands of servers like it.
This server
Across the catalogue