[CONFIDENTIAL ESCROW] Release a funded confidential escrow with CoFHE decryption. Decrypts the encrypted amount + fee server-side using the CoFHE threshold network, then calls releaseEscrow with the decrypted values + cryptographic signatures. The payee receives tokens via encrypted FHERC20 trans...
Part of the Kustodia Escrow server.
Free to start. No card required.
AI agents call release_confidential_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 release_confidential_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": {
"release_confidential_escrow": {}
}
}See the full Kustodia Escrow policy for all 36 tools.
These attack patterns abuse exactly the kind of access release_confidential_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.
[CONFIDENTIAL ESCROW] Release a funded confidential escrow with CoFHE decryption. Decrypts the encrypted amount + fee server-side using the CoFHE threshold network, then calls releaseEscrow with the decrypted values + cryptographic signatures. The payee receives tokens via encrypted FHERC20 transfer — no amounts visible. PRE-CONDITIONS: - Escrow must be in 'Funded' status - Only the payer, owner, or relayer can release. 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 release_confidential_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.
release_confidential_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 release_confidential_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 release_confidential_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.
release_confidential_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.