search_public
AI agents call search_public 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.
Despite the empty description, the tool name 'search_public' combined with context from the server's stated read-only purpose and the pattern of sibling tools (all get_* queries) strongly indicates this is a retrieval operation. No evidence suggests data modification, deletion, code execution, or financial operations.
From the tool's definition Server is described as 'read-only interface for querying markets, wallets, and order books' and sibling tools are all get_* operations. Tool name 'search_public' follows the query/retrieve pattern consistent with Read category tools.
Attacks that exploit this kind of access
search_public. 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_public: 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_public 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_public 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_public. 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_public is provided by the Polymarket MCP server (pr1m8/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 →