send_message
Send a message on a job to a specific other participant. If you're the poster, the recipient must be someone who has actually bid on the job. If you're a bidder, the recipient must be the poster.
This record as markdown: /tools/com-freelanceclearing-marketplace/send-message.md
What send_message does on Freelance Clearing
AI agents use send_message to create or update resources in Freelance Clearing, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freelance Clearing environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | The recipient's user id |
job_id | string | Yes | The job's UUID |
content | string | Yes | Message content |
Parameters from the server's own tool schema.
Why send_message is rated Medium
An AI agent can call send_message faster than any human can review: one bad instruction and it creates or modifies resources in Freelance Clearing by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs send_message 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 send_message, this is the rule to start with:
send_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 send_message call is checked against it from then on.
Questions about send_message
Send a message on a job to a specific other participant. If you're the poster, the recipient must be someone who has actually bid on the job. If you're a bidder, the recipient must be the poster. It is categorised as a Write tool in the Freelance Clearing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
send_message accepts 3 parameters: to, job_id, content. Required: to, job_id, content. 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 send_message: 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.
send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_message 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 send_message. 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.
send_message 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