List documents in the local workspace registry.
AI agents call pageindex_local_list_documents to retrieve information from Pageindex Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about indexed documents in the local workspace. It has no side effects—it neither modifies, deletes, nor executes any operations. The blast radius of misuse is minimal; an agent could learn what documents are indexed but cannot alter or remove them. This is a straightforward read operation.
From the tool's definition Tool name 'list_documents' and description 'List documents in the local workspace registry' indicate retrieval of document metadata without modification or deletion.
Attacks that exploit this kind of access
List documents in the local workspace registry. It is categorised as a Read tool in the Pageindex Local MCP Server, which means it retrieves data without modifying state.
Register the Pageindex Local MCP server in PolicyLayer and add a rule for pageindex_local_list_documents: 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 Pageindex Local. Nothing to install.
pageindex_local_list_documents 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 pageindex_local_list_documents 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 pageindex_local_list_documents. 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.
pageindex_local_list_documents is provided by the Pageindex Local MCP server (jamesbubenik/pageindex-local-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 →