AI agents call list_series to retrieve information from Lyceum 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 and enumerates metadata about series in a Calibre library. It has no side effects, does not modify data, and only performs informational lookups. The low severity reflects that exposing a library's series catalog presents minimal risk to system integrity.
From the tool's definition Tool 'list_series' returns series name and count without modification. Description indicates it 'List all series' and explicitly notes to use a separate tool ('list_books_by_series') to retrieve books in a series.
Attacks that exploit this kind of access
List all series in the library with book counts. Each result includes the series name and count. To get books in a series, use list_books_by_series with the series_id from a book. It is categorised as a Read tool in the Lyceum MCP Server, which means it retrieves data without modifying state.
Register the Lyceum MCP server in PolicyLayer and add a rule for list_series: 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 Lyceum. Nothing to install.
list_series 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_series 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_series. 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_series is provided by the Lyceum MCP server (matthewp/lyceum). 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 →