get_books
AI agents call get_books 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 order book data (CLOB - Central Limit Order Book) from Polymarket, which is a read-only query operation with no side effects. The server explicitly advertises itself as providing a 'read-only interface'. Even though the description is empty, the name pattern and server context strongly indicate this retrieves rather than modifies data.
From the tool's definition Tool name 'get_books' with sibling tools including 'get_book', 'get_activity', 'get_positions', 'get_price_history' and server description stating 'read-only interface for querying markets, wallets, and order books'.
Attacks that exploit this kind of access
get_books. 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 get_books: 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.
get_books 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_books 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_books. 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_books 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 →