Search for stock tickers by symbol or company name. Returns matching tickers.
AI agents call search_ticker to retrieve information from Lynx Mi/lynx Mi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns ticker information based on search criteria. It is a passive read operation that queries a data source without side effects, modifications, or irreversible actions. The low severity reflects that misuse would only expose publicly available ticker symbol information.
From the tool's definition Tool name 'search_ticker' and description 'Search for stock tickers by symbol or company name. Returns matching tickers.' indicate a query/lookup operation with no data modification, deletion, or execution of code or financial transactions.
Attacks that exploit this kind of access
Search for stock tickers by symbol or company name. Returns matching tickers. It is categorised as a Read tool in the Lynx Mi/lynx Mi MCP Server, which means it retrieves data without modifying state.
Register the Lynx Mi/lynx Mi MCP server in PolicyLayer and add a rule for search_ticker: 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 Lynx Mi/lynx Mi. Nothing to install.
search_ticker 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 search_ticker 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 search_ticker. 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.
search_ticker is provided by the Lynx Mi/lynx Mi MCP server (lynx-mi/lynx-mi-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 →