Pay SOL or tokens to a destination address using the Cloaked Agent spending account. Use this for x402 payments or any transfer within the agent
Part of the Cloaked Agent server.
Free to start. No card required.
AI agents use cloak_pay to initiate financial transactions through Cloaked Agent. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
cloak_pay moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
{
"version": "1",
"default": "deny",
"tools": {
"cloak_pay": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}See the full Cloaked Agent policy for all 14 tools.
These attack patterns abuse exactly the kind of access cloak_pay gives an agent. Each links to the full case and the policy that stops it:
Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Pay SOL or tokens to a destination address using the Cloaked Agent spending account. Use this for x402 payments or any transfer within the agent. It is categorised as a Financial tool in the Cloaked Agent MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Cloaked Agent MCP server in PolicyLayer and add a rule for cloak_pay: 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 Cloaked Agent. Nothing to install.
cloak_pay 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 cloak_pay 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 cloak_pay. 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.
cloak_pay is provided by the Cloaked Agent MCP server (@cloakedagent/sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cloaked Agent 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.