List all libraries (repos) accessible to the authenticated user.
AI agents call list_libraries to retrieve information from Seafile MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates data (accessible libraries) without modifying, deleting, or executing any operations. It is a read-only query against the Seafile server. Severity is low because listing accessible libraries has minimal blast radius — it exposes metadata about available storage but does not modify or delete anything, and the data returned is already accessible to the authenticated user.
From the tool's definition Tool name is 'list_libraries' and description states it 'List all libraries (repos) accessible to the authenticated user' — a pure query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all libraries (repos) accessible to the authenticated user. It is categorised as a Read tool in the Seafile MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Seafile MCP Server MCP server in PolicyLayer and add a rule for list_libraries: 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 Seafile MCP Server. Nothing to install.
list_libraries 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_libraries 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_libraries. 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_libraries is provided by the Seafile MCP Server MCP server (setugk/seafile-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 →