data_buy
Pays for and immediately fetches one resource from the catalogue (see data_list_for_sale) in a single call — signs the payment, settles it from your wallet, and returns the resource data plus a settlement receipt.
This record as markdown: /tools/com-focxle-afos/data-buy.md
What data_buy does on AFOS — Agentic Financial OS
AI agents use data_buy to commit financial operations through AFOS — Agentic Financial OS, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
params | object | — | Inputs the resource needs, e.g. {"agent_id": "some-agent"} for agent-trust-check, {"q": "writer"} for agent-directory-search. Every resource requires input; see |
resource_id | string | Yes | The resource_id from data_list_for_sale, e.g. "agent-trust-check". |
Parameters from the server's own tool schema.
Why data_buy is rated Critical
Directly moves USDC funds from wallet to purchase data resources.
From the tool's definition signs the payment, settles it from your wallet
Attacks that exploit this kind of access
The rule that runs data_buy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AFOS — Agentic Financial OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_buy, this is the rule to start with:
Any call to data_buy is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AFOS — Agentic Financial OS, apply this rule, and every data_buy call is checked against it from then on.
Questions about data_buy
Pays for and immediately fetches one resource from the catalogue (see data_list_for_sale) in a single call — signs the payment, settles it from your wallet, and returns the resource data plus a settlement receipt. It is categorised as a Financial tool in the AFOS — Agentic Financial OS MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
data_buy accepts 2 parameters: params, resource_id. Required: resource_id. The full parameter table on this page comes from the server's own tool schema.
Register the AFOS — Agentic Financial OS MCP server in PolicyLayer and add a rule for data_buy: 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 AFOS — Agentic Financial OS. Nothing to install.
data_buy is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the data_buy 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 data_buy. 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.
data_buy is provided by the AFOS — Agentic Financial OS MCP server (https://focxle.com/api/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AFOS — Agentic Financial OS, and thousands of servers like it.
Across the catalogue