[WEB3 ESCROW] Fund an existing on-chain escrow by batching approve + fundEscrow. FOR AGENTIC WALLETS (Coinbase AgentKit, server-side EOA). Human users with browser wallets (MetaMask) should fund via the Kustodia web3 dashboard. PRE-CONDITIONS: 1. Escrow must be in 'Created' status 2. The signing ...
Part of the Kustodia Escrow server.
Free to start. No card required.
AI agents call fund_web3_escrow to retrieve information from Kustodia Escrow 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 fund_web3_escrow 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": {
"fund_web3_escrow": {}
}
}See the full Kustodia Escrow policy for all 36 tools.
These attack patterns abuse exactly the kind of access fund_web3_escrow 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.
[WEB3 ESCROW] Fund an existing on-chain escrow by batching approve + fundEscrow. FOR AGENTIC WALLETS (Coinbase AgentKit, server-side EOA). Human users with browser wallets (MetaMask) should fund via the Kustodia web3 dashboard. PRE-CONDITIONS: 1. Escrow must be in 'Created' status 2. The signing wallet must be the PAYER registered in the escrow 3. Wallet must have sufficient token balance KEY SELECTION: - If you pass agent_private_key, that key signs the tx (Coinbase AgentKit flow) - If omitted, the platform relayer key signs (only works if relayer is the payer) - For ZeroDev gasless funding, use fund_with_session_key instead This tool automatically checks allowance, approves if needed, and calls fundEscrow.. It is categorised as a Read tool in the Kustodia Escrow MCP Server, which means it retrieves data without modifying state.
Register the Kustodia Escrow MCP server in PolicyLayer and add a rule for fund_web3_escrow: 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 Kustodia Escrow. Nothing to install.
fund_web3_escrow 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 fund_web3_escrow 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 fund_web3_escrow. 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.
fund_web3_escrow is provided by the Kustodia Escrow MCP server (kustodia/escrow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Kustodia Escrow 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.