Bucket a wallet's trades on a market into deciles of its lifetime.
AI agents call get_wallet_alpha_decay 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 retrieves and categorizes historical trading data from a wallet without modifying data, executing code, or causing side effects. It is a pure analytical read operation that examines existing market trades grouped by temporal lifecycle deciles. The read-only nature of the server combined with the get_ prefix and non-destructive analytical operation confirms Read category classification.
From the tool's definition Tool name contains 'get_' and description states it 'bucket[s] a wallet's trades' — a retrieval and analysis operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Bucket a wallet's trades on a market into deciles of its lifetime. 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_alpha_decay: 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_alpha_decay 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_alpha_decay 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_alpha_decay. 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_alpha_decay 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 →