Creates a new watchlist with specified symbols.
AI agents use create_watchlist to create or update resources in Alpaca MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alpaca MCP Server environment.
This tool creates a new watchlist, which is a reversible write operation. It does not execute trades, move money, delete data, or run arbitrary code. The blast radius is minimal—a watchlist is metadata for tracking interests and can be easily deleted or modified.
From the tool's definition Tool name 'create_watchlist' and description 'Creates a new watchlist with specified symbols' indicate data creation/modification. Watchlists are user-managed collections that organize assets for tracking purposes.
Attacks that exploit this kind of access
Creates a new watchlist with specified symbols. It is categorised as a Write tool in the Alpaca MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alpaca MCP Server MCP server in PolicyLayer and add a rule for create_watchlist: 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.
create_watchlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_watchlist 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 create_watchlist. 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.
create_watchlist 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 →