List files that failed to parse during AST indexing with their error messages.
AI agents call list_indexing_errors to retrieve information from Codeviewer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool has no side effects. It only reads and reports metadata about indexing failures within the code review workflow. An AI agent misusing it could only gather information about parsing errors, posing minimal risk. It does not modify state, execute code, or delete data.
From the tool's definition The tool lists files that failed to parse and returns error messages—it retrieves diagnostic information without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
List files that failed to parse during AST indexing with their error messages. It is categorised as a Read tool in the Codeviewer MCP Server, which means it retrieves data without modifying state.
Register the Codeviewer MCP server in PolicyLayer and add a rule for list_indexing_errors: 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 Codeviewer. Nothing to install.
list_indexing_errors 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 list_indexing_errors 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 list_indexing_errors. 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.
list_indexing_errors is provided by the Codeviewer MCP server (master0ffate/codeviewer-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 →