Delete a stock holding by ID.
AI agents call delete_stock_holding to permanently remove resources in Corpus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes stock holding data without the ability to undo the action. Deletion of financial records is irreversible and could result in loss of critical portfolio tracking information. While not directly moving money, it destructively modifies financial records that are essential to net worth tracking and portfolio management.
From the tool's definition Tool name 'delete_stock_holding' and description 'Delete a stock holding by ID' explicitly indicate irreversible deletion of financial asset records.
Attacks that exploit this kind of access
Delete a stock holding by ID. It is categorised as a Destructive tool in the Corpus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Corpus MCP Server MCP server in PolicyLayer and add a rule for delete_stock_holding: 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 Corpus MCP Server. Nothing to install.
delete_stock_holding 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 delete_stock_holding 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 delete_stock_holding. 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.
delete_stock_holding is provided by the Corpus MCP Server MCP server (mathankarthik18/corpus-mcp). 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 →