Create Offramp Wallet
How to control PostV1InstancesReceiversBankAccountsOfframpWallets ↓
AI agents use PostV1InstancesReceiversBankAccountsOfframpWallets to create or update resources in BlindPay MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlindPay MCP Server environment.
This tool creates a new offramp wallet entity, which is a reversible write operation. While it operates in a financial context (stablecoin payments), the tool itself does not directly move money or commit financial obligations—it creates infrastructure. However, due to the financial domain and potential for downstream financial transactions, severity is rated high.
From the tool's definition Tool name begins with 'Post' and description states 'Create Offramp Wallet', indicating creation of a new financial resource (wallet). The BlindPay server context indicates this operates on payment infrastructure and stablecoin operations.
Documented attack patterns abuse exactly the kind of access PostV1InstancesReceiversBankAccountsOfframpWallets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BlindPay MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for PostV1InstancesReceiversBankAccountsOfframpWallets:
{
"version": "1",
"default": "deny",
"tools": {
"PostV1InstancesReceiversBankAccountsOfframpWallets": {
"limits": [
{
"counter": "postv1instancesreceiversbankaccountsofframpwallets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}PostV1InstancesReceiversBankAccountsOfframpWallets stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create Offramp Wallet. It is categorised as a Write tool in the BlindPay MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BlindPay MCP Server MCP server in PolicyLayer and add a rule for PostV1InstancesReceiversBankAccountsOfframpWallets: 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 BlindPay MCP Server. Nothing to install.
PostV1InstancesReceiversBankAccountsOfframpWallets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the PostV1InstancesReceiversBankAccountsOfframpWallets 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 PostV1InstancesReceiversBankAccountsOfframpWallets. 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.
PostV1InstancesReceiversBankAccountsOfframpWallets is provided by the BlindPay MCP Server MCP server (blindpaylabs/blindpay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BlindPay MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
81 BlindPay MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.