get_account_info
A read tool on the Alpaca MCP server.
This record as markdown: /tools/cliffsgpt-alpaca-mcp-clone/get-account-info.md
What get_account_info does on Alpaca MCP Server
AI agents call get_account_info to retrieve information from Alpaca MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_account_info is rated Low
This tool retrieves account information, which is a read operation with no side effects. However, severity is elevated to 'medium' rather than 'low' because account information (holdings, balances, positions) is sensitive financial data that could be exploited if exposed to unauthorized agents or exfiltrated.
From the tool's definition Tool name 'get_account_info' on a trading API server indicates retrieval of account data without modification. The server context (Alpaca Trading API) and sibling tools like 'get_all_assets' and 'get_asset_info' confirm this is a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_account_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Alpaca MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_account_info, this is the rule to start with:
get_account_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Alpaca MCP Server, apply this rule, and every get_account_info call is checked against it from then on.
Questions about get_account_info
get_account_info is a read tool on the Alpaca MCP Server MCP server. It is categorised as a Read tool in the Alpaca MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Alpaca MCP Server 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 MCP Server. 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 MCP server (cliffsgpt/alpaca-mcp-clone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Alpaca MCP Server, and thousands of servers like it.
This server
Across the catalogue