get_position
Open position for a single market, or None if no position.
This record as markdown: /tools/0xdegenmo-lighter-mcp/get-position.md
What get_position does on Lighter MCP
AI agents call get_position 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_position is rated Low
This tool queries and returns existing position information for a user on a specific market. It performs no writes, deletions, executions, or financial transactions—it only retrieves data. While the Lighter server deals with financial trading, this specific tool is a non-destructive read operation that poses minimal risk if called by an AI agent, as it cannot create, modify, or close positions.
From the tool's definition Tool name 'get_position' and description 'Open position for a single market, or None if no position' indicate a read-only query that retrieves position data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_position 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_position, this is the rule to start with:
get_position 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_position call is checked against it from then on.
Questions about get_position
Open position for a single market, or None if no position. 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_position: 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_position 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_position 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_position. 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_position 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