remove_stock
AI agents call remove_stock to permanently remove resources in Financial MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'remove_stock' strongly implies irreversible removal of a stock from a portfolio. Given the sibling tool 'add_stock' exists (a clear counterpart), this tool likely deletes a stock entry from the user's portfolio. Removal of portfolio data is likely irreversible (Destructive).
From the tool's definition Tool name 'remove_stock' on a Financial MCP Server with portfolio management capabilities; description is empty and uninformative.
Attacks that exploit this kind of access
remove_stock. It is categorised as a Destructive tool in the Financial MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Financial MCP Server MCP server in PolicyLayer and add a rule for remove_stock: 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 Financial MCP Server. Nothing to install.
remove_stock is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_stock 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 remove_stock. 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.
remove_stock is provided by the Financial MCP Server MCP server (osamadev/financial_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 →