AI agents call list_files to retrieve information from Scholar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration of indexed files and returns their symbol counts. It is a read-only query operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an AI agent could at most enumerate the library contents, which is already visible to authorized users of the system. Classified as Read with low severity.
From the tool's definition Tool name 'list_files' and description 'List all indexed files with their symbol counts' indicate a retrieval operation that queries metadata about indexed ebooks without modifying, executing, or deleting data.
Attacks that exploit this kind of access
List all indexed files with their symbol counts. It is categorised as a Read tool in the Scholar MCP Server, which means it retrieves data without modifying state.
Register the Scholar MCP server in PolicyLayer and add a rule for list_files: 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 Scholar. Nothing to install.
list_files 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_files 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_files. 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_files is provided by the Scholar MCP server (unlomtrois/little-librarian). 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 →