get_status

A read tool on the Lighter MCP server.

SERVERLighter MCP SOURCE0xdegenmo/lighter-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xdegenmo-lighter-mcp/get-status.md

WHAT IT DOES

What get_status does on Lighter MCP

AI agents call get_status 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.

RISK

Why get_status is rated Low

Despite the empty description lowering confidence slightly, the naming convention and peer tools strongly indicate this is a status query operation with no side effects. Read operations on a financial platform carry low severity when they only retrieve data.

From the tool's definition Tool name is 'get_status' with empty description. The verb 'get' indicates retrieval without modification. Context from sibling tools (all read-only queries like 'get_balance', 'get_candles', 'get_orderbook') suggests this also retrieves state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_status 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_status, this is the rule to start with:

get_status Allowed

get_status 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_status": {}
  }
}

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

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

FAQ

Questions about get_status

What does the get_status tool do? +

get_status is a read tool on the Lighter MCP server. It is categorised as a Read tool in the Lighter MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_status? +

Register the Lighter MCP server in PolicyLayer and add a rule for get_status: 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.

What risk level is get_status? +

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

Can I rate-limit get_status? +

Yes. Add a rate_limit block to the get_status 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_status completely? +

Set action: deny in the PolicyLayer policy for get_status. 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_status? +

get_status 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.

KEEP EXPLORING

More on Lighter, and thousands of servers like it.

This server

All 20 Lighter tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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