AI agents use submit_cctp_offramp to commit financial operations through SpherePay — usually the final step of a payment, billing, or trading workflow. A call moves real money.
CCTP offramp operations involve moving cryptocurrency assets off-chain, which is a financial transaction that commits or moves funds. Given the server context (SpherePay managing transfers, wallets, bank accounts) and the 'offramp' terminology indicating a crypto-to-fiat or cross-chain asset movement, this tool almost certainly executes a financial operation.
From the tool's definition Tool name 'submit_cctp_offramp' on SpherePay server, which manages 'transfers' and financial operations; 'offramp' implies converting/moving cryptocurrency funds off a blockchain (CCTP = Cross-Chain Transfer Protocol)
Attacks that exploit this kind of access
submit_cctp_offramp. It is categorised as a Financial tool in the SpherePay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the SpherePay MCP server in PolicyLayer and add a rule for submit_cctp_offramp: 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 SpherePay. Nothing to install.
submit_cctp_offramp 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 submit_cctp_offramp 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 submit_cctp_offramp. 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.
submit_cctp_offramp is provided by the SpherePay MCP server (danchev/spherepay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →