get_option_contracts
A read tool on the Alpaca MCP server.
This record as markdown: /tools/cliffsgpt-alpaca-mcp-clone/get-option-contracts.md
What get_option_contracts does on Alpaca MCP Server
AI agents call get_option_contracts to retrieve information from Alpaca MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_option_contracts is rated Low
This tool retrieves or queries options contract information without modifying, executing, or deleting any data. The absence of a description lowers confidence slightly, but the naming pattern and sibling tools (get_account_info, get_all_assets, get_asset_info) strongly suggest a read-only query for market data. No financial transaction or destructive capability is indicated.
From the tool's definition Tool name 'get_option_contracts' suggests retrieval of options contract data. No description provided, but the verb 'get' and context within an Alpaca trading server (which includes read-only tools like 'get_account_info', 'get_all_assets', 'get_asset_info')…
Attacks that exploit this kind of access
The rule that runs get_option_contracts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Alpaca MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_option_contracts, this is the rule to start with:
get_option_contracts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Alpaca MCP Server, apply this rule, and every get_option_contracts call is checked against it from then on.
Questions about get_option_contracts
get_option_contracts is a read tool on the Alpaca MCP Server MCP server. It is categorised as a Read tool in the Alpaca MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Alpaca MCP Server MCP server in PolicyLayer and add a rule for get_option_contracts: 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 Server. Nothing to install.
get_option_contracts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_option_contracts 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 get_option_contracts. 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.
get_option_contracts is provided by the Alpaca MCP Server MCP server (cliffsgpt/alpaca-mcp-clone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Alpaca MCP Server, and thousands of servers like it.
This server
Across the catalogue