Update an existing watchlist.
AI agents use update_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 or modifies data (watchlist contents) in a reversible manner. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), move money (would be Financial), or merely read data (would be Read). The severity is medium because misuse could affect investment decision-making by poisoning watchlist data, but the impact is limited to one user's watchlist and is reversible.
From the tool's definition Tool name is 'update_watchlist' and description states 'Update an existing watchlist.' The verb 'update' indicates modification of existing data (a watchlist), which is a reversible write operation.
Attacks that exploit this kind of access
Update an existing watchlist. 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 update_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.
update_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 update_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 update_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.
update_watchlist is provided by the Alpaca MCP Server MCP server (metachain-org/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 →