compound_percentage
AI agents call compound_percentage to retrieve information from PolyMarket MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests a mathematical or analytical computation (likely calculating compound percentage returns or similar metrics) on existing market data. The server's stated purpose is data exploration and navigation of PolyMarket events. Without explicit evidence of side effects, writes, execution capabilities, or financial operations, this appears to be a read-only analytics tool.
From the tool's definition Tool name 'compound_percentage' suggests a calculation or data retrieval operation. Server context indicates data exploration and analytics across prediction markets. No description provided, limiting certainty.
Attacks that exploit this kind of access
compound_percentage. It is categorised as a Read tool in the PolyMarket MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PolyMarket MCP Server MCP server in PolicyLayer and add a rule for compound_percentage: 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 MCP Server. Nothing to install.
compound_percentage 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 compound_percentage 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 compound_percentage. 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.
compound_percentage is provided by the PolyMarket MCP Server MCP server (undiabler/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 →