Get detailed information about a specific function in OpenZeppelin Contracts
AI agents call get_oz_function 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 tool retrieves documentation and metadata about OpenZeppelin contract functions. It performs a query/lookup operation that returns information without creating, modifying, deleting, or executing any code. The offline documentation nature and retrieval-focused purpose confirm this is purely a Read operation with minimal risk.
From the tool's definition Tool description states 'Get detailed information about a specific function' - a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Get detailed information about a specific function in OpenZeppelin Contracts. 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 get_oz_function: 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.
get_oz_function 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_oz_function 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_oz_function. 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_oz_function 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 →