get_account_info

A read tool on the Alpaca MCP server.

SERVERAlpaca MCP Server SOURCEcliffsgpt/alpaca-mcp-clone
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_account_info

What does the get_account_info tool do? +

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.

How do I enforce a policy on get_account_info? +

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.

What risk level is get_account_info? +

get_account_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_account_info? +

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.

How do I block get_account_info completely? +

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.

What MCP server provides get_account_info? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Alpaca MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.