Identity + total portfolio value for a Polymarket wallet.
AI agents call get_wallet_profile 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 queries publicly available information about a wallet on Polymarket (identity and portfolio value). It performs a straightforward read operation without creating, modifying, deleting, or executing any actions. The read-only nature of the server and the retrieval-focused description confirm this is a Read category tool.
From the tool's definition Tool is part of a 'Read-only MCP server' and retrieves 'Identity + total portfolio value for a Polymarket wallet' — a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Identity + total portfolio value for a Polymarket wallet. 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_profile: 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_profile 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_profile 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_profile. 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_profile 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 →