Obtain all available tickers for a specific exchange.
AI agents call list_exchange_tickers to retrieve information from Marketstack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of tickers without creating, modifying, deleting, or executing any operations. It retrieves reference data about available trading symbols on an exchange, which is a read-only information lookup. No irreversible actions, code execution, or financial transactions are performed.
From the tool's definition Tool description states 'Obtain all available tickers for a specific exchange' - a retrieval operation with no modification or side effects. Sibling tools all follow a 'get_' or 'list_' read-only pattern for financial data access.
Attacks that exploit this kind of access
Obtain all available tickers for a specific exchange. It is categorised as a Read tool in the Marketstack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Marketstack MCP Server MCP server in PolicyLayer and add a rule for list_exchange_tickers: 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 Marketstack MCP Server. Nothing to install.
list_exchange_tickers 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 list_exchange_tickers 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 list_exchange_tickers. 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.
list_exchange_tickers is provided by the Marketstack MCP Server MCP server (matteoantoci/mcp-marketstack). 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 →