AI agents use PostV1InstancesPayoutsStellar to commit financial operations through BlindPay MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates and sends a payout (money movement) on the Stellar blockchain, which is a stablecoin payment infrastructure. Executing this moves funds irreversibly on-chain, making it a Financial action with critical severity due to the potential for misuse to send payments to unintended recipients or drain funds.
From the tool's definition Create Payout on Stellar — initiates a financial payout transaction on the Stellar blockchain network
Documented attack patterns abuse exactly the kind of access PostV1InstancesPayoutsStellar 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 PostV1InstancesPayoutsStellar:
{
"version": "1",
"default": "deny",
"tools": {
"PostV1InstancesPayoutsStellar": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to PostV1InstancesPayoutsStellar is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create Payout on Stellar. It is categorised as a Financial tool in the BlindPay MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the BlindPay MCP Server MCP server in PolicyLayer and add a rule for PostV1InstancesPayoutsStellar: 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.
PostV1InstancesPayoutsStellar 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 PostV1InstancesPayoutsStellar 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 PostV1InstancesPayoutsStellar. 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.
PostV1InstancesPayoutsStellar 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.