Low Risk

index_status

获取当前RAG索引的状态和统计信息

How to control index_status ↓

What index_status does on ChatPPT-MCP

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

Low Risk

Why index_status needs a policy

This tool retrieves or queries status and statistical information about the RAG index. It performs no mutations, deletions, or external operations—it is purely informational and read-only in nature.

From the tool's definition Tool name 'index_status' and description '获取当前RAG索引的状态和统计信息' (Get current RAG index status and statistics) indicate a retrieval operation that queries index metadata without modification or side effects.

Documented attack patterns abuse exactly the kind of access index_status gives an agent:

How to control index_status

PolicyLayer is an MCP gateway — it sits between your AI agents and ChatPPT-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for index_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "index_status": {}
  }
}

index_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ChatPPT-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about index_status

What does the index_status tool do? +

获取当前RAG索引的状态和统计信息. It is categorised as a Read tool in the ChatPPT-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on index_status? +

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

What risk level is index_status? +

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

Can I rate-limit index_status? +

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

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

index_status is provided by the ChatPPT- MCP server (pingcy/app_chatppt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ChatPPT-MCP tool call.

Start from ChatPPT-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

4 ChatPPT-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.