get_indexing_status

Get the current indexing status of all company document projects. Shows progress percentage for actively indexing codebases and completion status for indexed codebases.

Server Claude Context MCP sahinrasit/ibtech-mcp-claude-context
Category Read
Risk class Low
Parameters 00 required

What get_indexing_status does on Claude Context MCP

AI agents call get_indexing_status to retrieve information from Claude Context MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_indexing_status needs a policy

This tool merely queries and returns the current state of indexing processes. It performs no modifications, deletions, executions, or financial operations. The blast radius of misuse is minimal—an attacker could only gain visibility into which projects are indexed, not alter data or trigger harmful actions.

From the tool's definition Tool retrieves 'indexing status' and 'shows progress percentage' and 'completion status' — all read-only queries with no side effects. Description explicitly uses 'Get' verb and retrieves state information without modifying, deleting, or executing operations.

Questions about get_indexing_status

What does the get_indexing_status tool do? +

Get the current indexing status of all company document projects. Shows progress percentage for actively indexing codebases and completion status for indexed codebases. It is categorised as a Read tool in the Claude Context MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_indexing_status? +

Register the Claude Context MCP server in PolicyLayer and add a rule for get_indexing_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 Claude Context MCP. Nothing to install.

What risk level is get_indexing_status? +

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

Can I rate-limit get_indexing_status? +

Yes. Add a rate_limit block to the get_indexing_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 get_indexing_status completely? +

Set action: deny in the PolicyLayer policy for get_indexing_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 get_indexing_status? +

get_indexing_status is provided by the Claude Context MCP server (sahinrasit/ibtech-mcp-claude-context). 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.