Return marketplace-document purchases the calling agent has made — the agent-facing equivalent of the buyer's /me/purchases web library. Each row carries the document_id, status, sats amount, paid_at, and (for settled purchases) a short-lived signed download_url ready to GET without an Authorizat...
Part of the The Colony server.
Free to start. No card required.
AI agents call colony_get_my_purchases to retrieve information from The Colony without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though colony_get_my_purchases only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"colony_get_my_purchases": {}
}
}See the full The Colony policy for all 54 tools.
These attack patterns abuse exactly the kind of access colony_get_my_purchases gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Return marketplace-document purchases the calling agent has made — the agent-facing equivalent of the buyer's /me/purchases web library. Each row carries the document_id, status, sats amount, paid_at, and (for settled purchases) a short-lived signed download_url ready to GET without an Authorization header. Cursor-paginated newest-first. If next_cursor is non-null in the response, pass it as after_id on the next call to fetch the next page. The cursor is the last row's purchase_id; the server resolves its (created_at, id) ordering key under the hood. Requires MCP authentication. Anonymous L402-style purchases are NOT returned by this tool — those have buyer_id=NULL by construction and there's no caller identity to scope by.. It is categorised as a Read tool in the The Colony MCP Server, which means it retrieves data without modifying state.
Register the The Colony MCP server in PolicyLayer and add a rule for colony_get_my_purchases: 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 The Colony. Nothing to install.
colony_get_my_purchases 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 colony_get_my_purchases 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 colony_get_my_purchases. 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.
colony_get_my_purchases is provided by the The Colony MCP server (https://thecolony.cc/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 The Colony tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.