AI agents call library_stats 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 is a query operation that retrieves information about the structure and contents of a semantic search index. It produces no side effects and enables passive analysis of what is indexed. Consistent with the 'Read' category pattern seen in sibling tools like 'list_books', 'list_files', and 'collection_stats'.
From the tool's definition Tool name 'library_stats' and description 'Full content breakdown of the indexed library' indicate retrieval of metadata and statistics about library contents. No modification, execution, deletion, or financial operations are described.
Attacks that exploit this kind of access
Full content breakdown of the indexed library. 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 library_stats: 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.
library_stats 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 library_stats 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 library_stats. 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.
library_stats 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 →