create_sample_dataset_from_portfolio_tool
AI agents use create_sample_dataset_from_portfolio_tool to create or update resources in Alpaca MCP Gold Standard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alpaca MCP Gold Standard environment.
The tool creates new data (a sample dataset) from existing portfolio information, which is a reversible write operation. It does not execute trades, delete data, or move money.
From the tool's definition Tool name 'create_sample_dataset_from_portfolio_tool' indicates it creates or generates a new dataset derived from portfolio data. The verb 'create' and context within a trading operations server suggest data generation/writing.
Attacks that exploit this kind of access
create_sample_dataset_from_portfolio_tool. It is categorised as a Write tool in the Alpaca MCP Gold Standard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alpaca MCP Gold Standard MCP server in PolicyLayer and add a rule for create_sample_dataset_from_portfolio_tool: 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 Gold Standard. Nothing to install.
create_sample_dataset_from_portfolio_tool 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 create_sample_dataset_from_portfolio_tool 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 create_sample_dataset_from_portfolio_tool. 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.
create_sample_dataset_from_portfolio_tool is provided by the Alpaca MCP Gold Standard MCP server (joravetz/alpaca-mcp-gold). 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 →