Add a new transaction to a stock holdind transaction_type: BUY or SELL
AI agents use add_stock_transaction to create or update resources in Corpus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Corpus MCP Server environment.
This tool creates new financial transaction records (BUY/SELL) in a portfolio tracking system. While it is reversible via delete_transaction (making it Write rather than Destructive), it directly modifies financial portfolio state and could misrepresent holdings if used incorrectly.
From the tool's definition Tool name 'add_stock_transaction' and description 'Add a new transaction to a stock holding' with transaction_type BUY or SELL indicates creation of financial transaction records.
Attacks that exploit this kind of access
Add a new transaction to a stock holdind transaction_type: BUY or SELL. It is categorised as a Write tool in the Corpus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Corpus MCP Server MCP server in PolicyLayer and add a rule for add_stock_transaction: 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.
add_stock_transaction 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 add_stock_transaction 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 add_stock_transaction. 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.
add_stock_transaction 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 →