Search OpenZeppelin Contracts documentation for guides, API references, and code examples
AI agents call search_oz_docs to retrieve information from OpenZeppelin Docs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search and retrieval tool that queries offline documentation. It returns information about contract APIs, functions, events, and guides without modifying any data, executing code, or triggering external operations. The sibling tools (get_oz_contract, get_oz_function, list_oz_modules, oz_index_status) similarly indicate read-only operations.
From the tool's definition Tool description states "Search OpenZeppelin Contracts documentation" with "retrieval" and "querying" mentioned in server description. No modification, deletion, or execution capabilities indicated.
Attacks that exploit this kind of access
Search OpenZeppelin Contracts documentation for guides, API references, and code examples. It is categorised as a Read tool in the OpenZeppelin Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenZeppelin Docs MCP Server MCP server in PolicyLayer and add a rule for search_oz_docs: 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 OpenZeppelin Docs MCP Server. Nothing to install.
search_oz_docs 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_oz_docs 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_oz_docs. 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_oz_docs is provided by the OpenZeppelin Docs MCP Server MCP server (pbuda/openzeppelin-docs-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 →