get_market
Get metadata for a single market by symbol (e.g. 'HYPE', 'ETH').
This record as markdown: /tools/0xdegenmo-lighter-mcp/get-market.md
What get_market does on Lighter MCP
AI agents call get_market to retrieve information from Lighter MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_market is rated Low
This tool queries and returns metadata about a market (e.g., 'HYPE', 'ETH'). It performs a read-only lookup with no ability to modify data, execute trades, delete data, or incur financial obligations. The blast radius of misuse is minimal—an agent could only retrieve information already publicly available on the DEX.
From the tool's definition Tool name 'get_market' and description 'Get metadata for a single market by symbol' indicate a query operation that retrieves market information without side effects.
Attacks that exploit this kind of access
The rule that runs get_market safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lighter MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_market, this is the rule to start with:
get_market 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 Lighter MCP, apply this rule, and every get_market call is checked against it from then on.
Questions about get_market
Get metadata for a single market by symbol (e.g. 'HYPE', 'ETH'). It is categorised as a Read tool in the Lighter MCP MCP Server, which means it retrieves data without modifying state.
Register the Lighter MCP server in PolicyLayer and add a rule for get_market: 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 Lighter MCP. Nothing to install.
get_market 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_market 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_market. 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_market is provided by the Lighter MCP server (0xdegenmo/lighter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lighter, and thousands of servers like it.
This server
Across the catalogue