Retrieve a specific automation by ID
AI agents call brale_get_automation to retrieve information from Brale API 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 data about an automation configuration without modifying, deleting, or executing any financial operations. It is a simple lookup/query operation that returns information. While it exists within a financial API server (Brale), the tool itself only reads existing data and does not move money, create accounts, or trigger any irreversible actions.
From the tool's definition Tool name contains 'get' and description states 'Retrieve a specific automation by ID', indicating a read-only query operation with no side effects.
Attacks that exploit this kind of access
Retrieve a specific automation by ID. It is categorised as a Read tool in the Brale API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Brale API MCP Server MCP server in PolicyLayer and add a rule for brale_get_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_get_automation 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 brale_get_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_get_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_get_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 →