trust_check_wallet
Checks whether a counterparty is safe to transact with, given nothing but its wallet address. Answers for ANY address on Base, including one that has never used Focxle, so it is usable on a counterparty you just met. Returns two blocks kept deliberately separate: onchain (wallet age, USDC balance...
This record as markdown: /tools/com-focxle-afos/trust-check-wallet.md
What trust_check_wallet does on AFOS — Agentic Financial OS
AI agents call trust_check_wallet to retrieve information from AFOS — Agentic Financial OS 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 |
|---|---|---|---|
wallet | string | Yes | The counterparty to check: a 0x wallet address on Base, or a Focxle agent id. A wallet address works even if that wallet has never transacted with us. |
Parameters from the server's own tool schema.
Why trust_check_wallet is rated Low
This is fundamentally a read operation that queries and returns blockchain and reputation data without side effects. While the data informs financial decisions on a Financial OS platform, the tool itself performs no financial transactions, does not execute code, and does not modify state.
From the tool's definition Tool description states it 'Checks whether a counterparty is safe to transact with' and 'Returns two blocks': onchain data (wallet age, balance, transaction count, OFAC screening, score) and focxle reputation data (tier, payment history, credit line).
Attacks that exploit this kind of access
The rule that runs trust_check_wallet 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 trust_check_wallet, this is the rule to start with:
trust_check_wallet 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 AFOS — Agentic Financial OS, apply this rule, and every trust_check_wallet call is checked against it from then on.
Questions about trust_check_wallet
Checks whether a counterparty is safe to transact with, given nothing but its wallet address. Answers for ANY address on Base, including one that has never used Focxle, so it is usable on a counterparty you just met. Returns two blocks kept deliberately separate: onchain (wallet age, USDC balance, transaction count, EOA vs smart account, OFAC SDN screening, and a 0-100 score labelled as inference from public data) and focxle (reputation earned from payments actually settled here, tier, on-time vs failed counts, credit line). Public chain facts are never blended with witnessed behaviour, so you can tell what we observed from what we inferred. Costs $0.02 in USDC. Callable with no account: ask without credentials and it returns the price and a URL you can pay directly from a wallet holding USDC. It is categorised as a Read tool in the AFOS — Agentic Financial OS MCP Server, which means it retrieves data without modifying state.
trust_check_wallet accepts 1 parameter: wallet. Required: wallet. 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 trust_check_wallet: 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.
trust_check_wallet 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 trust_check_wallet 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 trust_check_wallet. 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.
trust_check_wallet 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.
This server
Across the catalogue