Look up information about tickers.
AI agents call get_ticker_info 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 retrieves ticker information without creating, modifying, deleting, or executing operations. It has no side effects and poses minimal security risk—the blast radius of misuse would be limited to unauthorized access to publicly available market data. Classified as Read with low severity.
From the tool's definition Tool name 'get_ticker_info' and description 'Look up information about tickers' indicate a query/retrieval operation. The Marketstack server context confirms this provides 'access to financial market data' without modification capabilities.
Attacks that exploit this kind of access
Look up information about tickers. 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 get_ticker_info: 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.
get_ticker_info 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_ticker_info 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_ticker_info. 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_ticker_info 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 →