get_my_states
AI agents call get_my_states to retrieve information from Adsb Lol MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context within an aircraft tracking server (adsb.lol) indicates this tool retrieves data without modifying it. In the context of ADS-B flight tracking, 'states' likely refers to aircraft state vectors or flight states, which are read-only queries. Confidence is reduced to 0.7 due to the empty description, but the naming pattern and server context strongly suggest read-only behavior.
From the tool's definition Tool name 'get_my_states' suggests retrieval of state data. No description provided, but naming convention aligns with read operations (get_*) consistent with sibling tools like 'get_callsign', 'get_closest', 'get_faa_entry', and 'get_flights_by_aircraft'…
Attacks that exploit this kind of access
get_my_states. It is categorised as a Read tool in the Adsb Lol MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Adsb Lol MCP Server MCP server in PolicyLayer and add a rule for get_my_states: 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 Adsb Lol MCP Server. Nothing to install.
get_my_states 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_my_states 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_my_states. 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_my_states is provided by the Adsb Lol MCP Server MCP server (x86ed/adsb.lol-mcp). 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 →