Add a position to your portfolio with automatic cost basis averaging. Args: ticker: Stock ticker symbol shares: Number of shares purchased purchase_price: Price per share at purchase purchase_date: Date of purchase (YYYY-MM-DD format, optional) notes: Optional notes about the position
AI agents use add_portfolio_position to create or update resources in MaverickMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MaverickMCP environment.
This tool creates a new record in the user's portfolio system. While it modifies financial data (portfolio composition), it is reversible (positions can be removed or adjusted) and does not commit actual financial transactions or move money. It records investment intent/tracking rather than executing trades or executing irreversible deletions.
From the tool's definition Tool adds/creates a portfolio position with cost basis averaging. The description explicitly states 'Add a position to your portfolio', which is a create operation that modifies the user's portfolio data.
Documented attack patterns abuse exactly the kind of access add_portfolio_position gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MaverickMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_portfolio_position:
{
"version": "1",
"default": "deny",
"tools": {
"add_portfolio_position": {
"limits": [
{
"counter": "add_portfolio_position_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_portfolio_position stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a position to your portfolio with automatic cost basis averaging. Args: ticker: Stock ticker symbol shares: Number of shares purchased purchase_price: Price per share at purchase purchase_date: Date of purchase (YYYY-MM-DD format, optional) notes: Optional notes about the position. It is categorised as a Write tool in the MaverickMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Maverick MCP server in PolicyLayer and add a rule for add_portfolio_position: 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 MaverickMCP. Nothing to install.
add_portfolio_position 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_portfolio_position 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_portfolio_position. 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_portfolio_position is provided by the Maverick MCP server (wshobson/maverick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 MaverickMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 MaverickMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.