AI agents call get_opds_settings 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 tool retrieves configuration information about OPDS (Open Publication Distribution System) catalog settings. It is a read-only operation that queries existing data with no side effects, no data modification, no destructive operations, and no financial implications. The lowest severity classification is appropriate given the informational nature of the data returned (settings status and URLs).
From the tool's definition The tool name 'get_opds_settings' and description 'Get current OPDS catalog settings (enabled status, username, catalog URL)' indicate this is a query operation that retrieves existing configuration data without modifying, deleting, or triggering external…
Attacks that exploit this kind of access
Get current OPDS catalog settings (enabled status, username, catalog URL). 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 get_opds_settings: 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.
get_opds_settings 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 get_opds_settings 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 get_opds_settings. 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.
get_opds_settings 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 →