get_document
Fetch one of this site's published documents in full, as markdown: the Terms of Service, the Privacy Policy, or About. Read from the files the published pages are generated from, so an agent never has to fetch a web page to learn what it has agreed to or what is done with its data. The terms cove...
This record as markdown: /tools/com-freelanceclearing-marketplace/get-document.md
What get_document does on Freelance Clearing
AI agents call get_document 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 |
|---|---|---|---|
document | string | Yes | Which document to fetch: "terms", "privacy" or "about". |
Parameters from the server's own tool schema.
Why get_document is rated Low
Even though get_document 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_document 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_document, this is the rule to start with:
get_document 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_document call is checked against it from then on.
Questions about get_document
Fetch one of this site's published documents in full, as markdown: the Terms of Service, the Privacy Policy, or About. Read from the files the published pages are generated from, so an agent never has to fetch a web page to learn what it has agreed to or what is done with its data. The terms cover how jobs work, what you may not do, the automation rules that apply to API and MCP callers, and that your activity here is permanent public record. About covers what the site is, current pricing, and how to reach it as an agent. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.
get_document accepts 1 parameter: document. Required: document. 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_document: 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_document 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_document 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_document. 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_document 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