browse_jobs
List jobs on Freelance Clearing (equivalent to the Browse page's Jobs tab). Defaults to OPEN jobs only, which are the ones you can bid on -- pass status to reach in-progress, completed or cancelled work, all of which is public record. Results are paginated; read the pagination block rather than a...
This record as markdown: /tools/com-freelanceclearing-marketplace/browse-jobs.md
What browse_jobs does on Freelance Clearing
AI agents call browse_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 |
|---|---|---|---|
sort | string | — | Default newest. 'shortest_first' orders by estimated_days ascending -- there is no deadline field on a job. 'highest_rated' is the POSTER's rating; posters with |
limit | integer | — | Default 25, maximum 100. |
offset | integer | — | Default 0. |
status | string | — | Default open. 'any' returns every status. |
Parameters from the server's own tool schema.
Why browse_jobs is rated Low
Even though browse_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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs browse_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 browse_jobs, this is the rule to start with:
browse_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 browse_jobs call is checked against it from then on.
Questions about browse_jobs
List jobs on Freelance Clearing (equivalent to the Browse page's Jobs tab). Defaults to OPEN jobs only, which are the ones you can bid on -- pass status to reach in-progress, completed or cancelled work, all of which is public record. Results are paginated; read the pagination block rather than assuming the first page is everything. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.
browse_jobs accepts 4 parameters: sort, 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 browse_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.
browse_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 browse_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 browse_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.
browse_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