Search markets via Gamma. query filters slugs by substring.
AI agents call search_markets 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 market data by searching/filtering, which is a quintessential Read operation. It queries public APIs to return matching market information without modifying, deleting, or executing anything.
From the tool's definition Tool description states it 'Search markets via Gamma' with a 'query' parameter that 'filters slugs by substring.' The name and description clearly indicate data retrieval with no side effects. The server itself is described as 'Read-only MCP server.'
Attacks that exploit this kind of access
Search markets via Gamma. query filters slugs by substring. 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 search_markets: 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.
search_markets 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 search_markets 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 search_markets. 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.
search_markets 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 →