AI agents call get_account_info to retrieve information from Alpaca without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch or query account details from the Alpaca Trading API. Reading account information has no side effects and poses minimal risk if misused—an AI agent can see account balances and positions but cannot execute trades, cancel orders, or move money. The lack of description lowers confidence slightly, but the naming convention and server context are clear indicators of a read-only operation.
From the tool's definition Tool name 'get_account_info' and server context indicate this retrieves account information without modifying state. Sibling tools like 'get_all_assets', 'get_asset_info', and 'get_corporate_announcements' establish a pattern of Read operations on this server.
Attacks that exploit this kind of access
get_account_info. It is categorised as a Read tool in the Alpaca MCP Server, which means it retrieves data without modifying state.
Register the Alpaca MCP server in PolicyLayer and add a rule for get_account_info: 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 Alpaca. Nothing to install.
get_account_info 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 get_account_info 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 get_account_info. 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.
get_account_info is provided by the Alpaca MCP server (mfoster5303-1/alpaca-mcp-server). 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 →