Earliest known trade by this wallet — proxy for "Polymarket join date".
AI agents call get_wallet_first_trade to retrieve information from Polymarket Research without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation on public blockchain/market data. It queries when a wallet first traded on Polymarket, which is informational only with no side effects, no state changes, and no ability to modify or delete data.
From the tool's definition Tool description explicitly states it retrieves 'Earliest known trade by this wallet' and the server is described as 'Read-only MCP server'. The tool queries historical trading data without modifying or deleting anything.
Attacks that exploit this kind of access
Earliest known trade by this wallet — proxy for "Polymarket join date". It is categorised as a Read tool in the Polymarket Research MCP Server, which means it retrieves data without modifying state.
Register the Polymarket Research MCP server in PolicyLayer and add a rule for get_wallet_first_trade: 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 Polymarket Research. Nothing to install.
get_wallet_first_trade 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_wallet_first_trade 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_wallet_first_trade. 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_wallet_first_trade is provided by the Polymarket Research MCP server (yoppav/polymarket-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 →