Search for markets by keyword or phrase using slug filtering.
AI agents call search_markets to retrieve information from Polymarket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters market data based on search criteria. It has no side effects, does not modify state, execute code, delete data, or move funds. It is a straightforward information retrieval function typical of market data APIs. Low severity because misuse (e.g., excessive queries) poses minimal risk beyond potential API rate limiting.
From the tool's definition Tool performs 'search for markets by keyword or phrase using slug filtering' — a pure query operation with no data modification, deletion, or execution of external commands. All sibling tools on this server are also Read operations (get_*, search_*).
Documented attack patterns abuse exactly the kind of access search_markets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Polymarket, and nothing reaches the server without passing your rules. This is the rule we recommend for search_markets:
{
"version": "1",
"default": "deny",
"tools": {
"search_markets": {}
}
}search_markets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for markets by keyword or phrase using slug filtering. It is categorised as a Read tool in the Polymarket MCP Server, which means it retrieves data without modifying state.
Register the Polymarket 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. 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 MCP server (pab1it0/polymarket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Polymarket, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Polymarket tools catalogued and risk-classified — across an index of 43,000+ MCP servers.