oz_index_status

Check if the OpenZeppelin docs index is ready. Call this if other tools report the index is building.

Server OpenZeppelin Docs MCP Server pbuda/openzeppelin-docs-mcp
Category Read
Risk class Low
Parameters 00 required

What oz_index_status does on OpenZeppelin Docs MCP Server

AI agents call oz_index_status 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.

Why oz_index_status needs a policy

This tool retrieves the status of the documentation index without modifying, executing, or deleting any data. It is a simple query operation that returns state information, making it a Read category tool with low severity since misuse would only return status information without operational impact.

From the tool's definition Tool name 'oz_index_status' and description 'Check if the OpenZeppelin docs index is ready' indicate a status query operation with no side effects. The verb 'check' and the read-only nature of status inspection confirm this is a retrieval operation.

Questions about oz_index_status

What does the oz_index_status tool do? +

Check if the OpenZeppelin docs index is ready. Call this if other tools report the index is building. It is categorised as a Read tool in the OpenZeppelin Docs MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on oz_index_status? +

Register the OpenZeppelin Docs MCP Server MCP server in PolicyLayer and add a rule for oz_index_status: 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.

What risk level is oz_index_status? +

oz_index_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit oz_index_status? +

Yes. Add a rate_limit block to the oz_index_status 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.

How do I block oz_index_status completely? +

Set action: deny in the PolicyLayer policy for oz_index_status. 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.

What MCP server provides oz_index_status? +

oz_index_status 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.