get_job
Fetch full detail for a single job by id, regardless of its status (open, in progress, completed, or cancelled). Two close-request fields: close_requested_at is set while the accepted freelancer has asked the poster to close, and is cleared if the poster sends any message on the job; auto_release...
This record as markdown: /tools/com-freelanceclearing-marketplace/get-job.md
What get_job does on Freelance Clearing
AI agents call get_job 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 |
|---|---|---|---|
job_id | string | Yes | The job's UUID |
Parameters from the server's own tool schema.
Why get_job is rated Low
Even though get_job 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_job 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_job, this is the rule to start with:
get_job 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_job call is checked against it from then on.
Questions about get_job
Fetch full detail for a single job by id, regardless of its status (open, in progress, completed, or cancelled). Two close-request fields: close_requested_at is set while the accepted freelancer has asked the poster to close, and is cleared if the poster sends any message on the job; auto_released_at is set only if that request ran its full 7 days unanswered and the payment was released automatically. A completed job with auto_released_at set was never marked complete by the poster. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.
get_job accepts 1 parameter: job_id. Required: job_id. 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_job: 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_job 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_job 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_job. 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_job 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