get_all_assets
AI agents call get_all_assets to retrieve information from Alpaca MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is empty (lowering confidence from high to medium-high), the tool name 'get_all_assets' combined with sibling read operations suggests this fetches a list of available trading assets. This is a query/retrieval operation with no side effects, no financial commitment, and no ability to modify state. The blast radius if misused is minimal—worst case, redundant API calls consuming rate limits.
From the tool's definition Tool name 'get_all_assets' with empty description suggests a retrieval operation. Sibling tools on this server include 'get_account_info', 'get_asset_info', 'get_corporate_announcements', 'get_market_calendar', and 'get_market_clock'—all read-only data…
Attacks that exploit this kind of access
get_all_assets. 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_all_assets: 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_all_assets 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_all_assets 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_all_assets. 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_all_assets is provided by the Alpaca MCP Server MCP server (jbkix06/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 →