Create a new automation for automated deposit addresses or onramps
AI agents use brale_create_automation to commit financial operations through Brale API MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating automations for deposit addresses or onramps sets up recurring or automated financial operations. In the context of a stablecoin/financial API server, this establishes infrastructure that governs how funds are received and processed, making it a Financial category tool. Misuse could result in funds being routed incorrectly or unauthorized parties receiving deposits.
From the tool's definition 'Create a new automation for automated deposit addresses or onramps' — automations for deposits/onramps directly relate to financial flows and money movement infrastructure
Attacks that exploit this kind of access
Create a new automation for automated deposit addresses or onramps. It is categorised as a Financial tool in the Brale API MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Brale API MCP Server MCP server in PolicyLayer and add a rule for brale_create_automation: 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 Brale API MCP Server. Nothing to install.
brale_create_automation 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 brale_create_automation 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 brale_create_automation. 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.
brale_create_automation is provided by the Brale API MCP Server MCP server (stablecoinxyz/brale-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →