get_tickers

Get tickers for all instruments of a given type

SERVERDerive MCP Server SOURCEaadarshvelu/derive-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/aadarshvelu-derive-mcp/get-tickers.md

WHAT IT DOES

What get_tickers does on Derive MCP Server

AI agents call get_tickers to retrieve information from Derive MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_tickers is rated Low

This tool retrieves ticker information for financial instruments. It performs a read-only query with no side effects, does not modify data, does not execute arbitrary operations, and does not commit financial transactions. While it accesses financial market data, the tool itself merely queries and returns information without enabling trades, transfers, or other actionable financial operations.

From the tool's definition Tool name 'get_tickers' and description 'Get tickers for all instruments of a given type' indicate a query operation that retrieves market data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tickers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Derive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tickers, this is the rule to start with:

get_tickers Allowed

get_tickers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tickers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Derive MCP Server, apply this rule, and every get_tickers call is checked against it from then on.

FAQ

Questions about get_tickers

What does the get_tickers tool do? +

Get tickers for all instruments of a given type. It is categorised as a Read tool in the Derive MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tickers? +

Register the Derive MCP Server MCP server in PolicyLayer and add a rule for get_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 Derive MCP Server. Nothing to install.

What risk level is get_tickers? +

get_tickers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tickers? +

Yes. Add a rate_limit block to the get_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.

How do I block get_tickers completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_tickers? +

get_tickers is provided by the Derive MCP Server MCP server (aadarshvelu/derive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Derive MCP Server, and thousands of servers like it.

This server

All 15 Derive MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →