Get a trader
AI agents call get_trader_trades to retrieve information from Limitless MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical or current trade information for a specific trader from blockchain subgraphs. It has no side effects—it only queries and returns data. No modifications, deletions, executions, or financial transactions are indicated. Read operations have low severity as they cannot damage systems or cause irreversible harm, though the blast radius depends on what data is exposed.
From the tool's definition Tool name 'get_trader_trades' and context indicate retrieval of on-chain trader trade data from subgraphs. The server description states 'Every tool queries the subgraphs for on-chain data.' The verb 'get' is characteristic of read operations.
Attacks that exploit this kind of access
Get a trader. It is categorised as a Read tool in the Limitless MCP MCP Server, which means it retrieves data without modifying state.
Register the Limitless MCP server in PolicyLayer and add a rule for get_trader_trades: 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 Limitless MCP. Nothing to install.
get_trader_trades 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_trader_trades 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_trader_trades. 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_trader_trades is provided by the Limitless MCP server (paulieb14/limitless-subgraphs). 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 →