AI agents use PostV1InstancesReceiversBankAccounts 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 bank account records within a payment infrastructure system. While the immediate action is creating/adding data (Write category), the context of a stablecoin payment system and the fact that bank accounts are being registered makes this high severity due to potential downstream financial implications—misuse could enable fraudulent account registration, unauthorized fund transfers, or payment…
From the tool's definition Tool name 'PostV1InstancesReceiversBankAccounts' with description 'Add Bank Account' indicates a POST operation that creates new financial account records. The 'Post' HTTP verb and 'Add' action confirm data creation.
Documented attack patterns abuse exactly the kind of access PostV1InstancesReceiversBankAccounts 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 PostV1InstancesReceiversBankAccounts:
{
"version": "1",
"default": "deny",
"tools": {
"PostV1InstancesReceiversBankAccounts": {
"limits": [
{
"counter": "postv1instancesreceiversbankaccounts_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}PostV1InstancesReceiversBankAccounts 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.
Add Bank Account. 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 PostV1InstancesReceiversBankAccounts: 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.
PostV1InstancesReceiversBankAccounts 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 PostV1InstancesReceiversBankAccounts 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 PostV1InstancesReceiversBankAccounts. 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.
PostV1InstancesReceiversBankAccounts 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.