List all 61 library sources with descriptions and capabilities.
AI agents call library_list_sources to retrieve information from Alexandria MCP 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 metadata about available library sources. It performs a listing/retrieval operation with no capability to modify, delete, or execute external operations. The action is informational only, making it a Read category tool with low severity—exposing library source names and capabilities poses minimal risk to the system or data.
From the tool's definition Tool name 'library_list_sources' and description 'List all 61 library sources with descriptions and capabilities' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all 61 library sources with descriptions and capabilities. It is categorised as a Read tool in the Alexandria MCP MCP Server, which means it retrieves data without modifying state.
Register the Alexandria MCP server in PolicyLayer and add a rule for library_list_sources: 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 Alexandria MCP. Nothing to install.
library_list_sources 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_list_sources 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_list_sources. 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_list_sources is provided by the Alexandria MCP server (the-40-thieves/alexandria-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 →