Get Offramp Wallet
How to control GetV1InstancesReceiversBankAccountsOfframpWalletsById ↓
AI agents call GetV1InstancesReceiversBankAccountsOfframpWalletsById to retrieve information from BlindPay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an offramp wallet associated with a receiver's bank account. The 'Get' operation is a read-only query that does not create, modify, delete, or execute any financial transactions. While it accesses payment infrastructure data, the tool itself merely retrieves existing wallet information without side effects.
From the tool's definition Tool name uses 'Get' prefix and description states 'Get Offramp Wallet', indicating a retrieval operation with no modification or destructive action.
Documented attack patterns abuse exactly the kind of access GetV1InstancesReceiversBankAccountsOfframpWalletsById 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 GetV1InstancesReceiversBankAccountsOfframpWalletsById:
{
"version": "1",
"default": "deny",
"tools": {
"GetV1InstancesReceiversBankAccountsOfframpWalletsById": {}
}
} GetV1InstancesReceiversBankAccountsOfframpWalletsById is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Offramp Wallet. It is categorised as a Read tool in the BlindPay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BlindPay MCP Server MCP server in PolicyLayer and add a rule for GetV1InstancesReceiversBankAccountsOfframpWalletsById: 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.
GetV1InstancesReceiversBankAccountsOfframpWalletsById 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 GetV1InstancesReceiversBankAccountsOfframpWalletsById 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 GetV1InstancesReceiversBankAccountsOfframpWalletsById. 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.
GetV1InstancesReceiversBankAccountsOfframpWalletsById 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.