Authorize Token Stellar
AI agents use PostV1InstancesPayoutsStellarAuthorize to commit financial operations through BlindPay MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Authorizing a Stellar payout directly triggers or approves a blockchain-based financial transfer. This falls under Financial as it commits a financial obligation/payment on the Stellar network. The blast radius is critical because misuse could result in irreversible stablecoin transfers on a public blockchain.
From the tool's definition 'Authorize Token Stellar' within a 'stablecoin payment infrastructure' server that handles 'process payouts' — authorizing a payout on the Stellar blockchain commits a financial transaction.
Documented attack patterns abuse exactly the kind of access PostV1InstancesPayoutsStellarAuthorize 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 PostV1InstancesPayoutsStellarAuthorize:
{
"version": "1",
"default": "deny",
"tools": {
"PostV1InstancesPayoutsStellarAuthorize": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to PostV1InstancesPayoutsStellarAuthorize is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Authorize Token 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 PostV1InstancesPayoutsStellarAuthorize: 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.
PostV1InstancesPayoutsStellarAuthorize 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 PostV1InstancesPayoutsStellarAuthorize 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 PostV1InstancesPayoutsStellarAuthorize. 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.
PostV1InstancesPayoutsStellarAuthorize 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.