Check whether the code search index is fully up to date with the file system.
AI agents call ready to retrieve information from Codesearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only status check that queries the current state of the code search index. It has no side effects, does not execute code, does not modify data, and does not affect external systems. The tool simply returns whether the index is synchronized with the file system, making it a low-risk Read operation with minimal blast radius even if misused.
From the tool's definition Tool name 'ready' and description 'Check whether the code search index is fully up to date' indicate a status query that retrieves information about index state without modifying data or triggering operations.
Attacks that exploit this kind of access
Check whether the code search index is fully up to date with the file system. It is categorised as a Read tool in the Codesearch MCP Server, which means it retrieves data without modifying state.
Register the Codesearch MCP server in PolicyLayer and add a rule for ready: 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 Codesearch. Nothing to install.
ready 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 ready 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 ready. 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.
ready is provided by the Codesearch MCP server (microsoft/tscodesearch). 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 →