Get the table of contents for a specific library source.
AI agents call get_library_toc to retrieve information from DM20 Protocol 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 (table of contents) from a library/rulebook source. It performs a read-only lookup operation. There is no code execution, data modification, deletion, or financial impact. The blast radius of misuse is minimal—returning a table of contents poses no security or game-state risk.
From the tool's definition Tool name is 'get_library_toc' and description states 'Get the table of contents for a specific library source' — a retrieval operation with no mutation or side effects.
Attacks that exploit this kind of access
Get the table of contents for a specific library source. It is categorised as a Read tool in the DM20 Protocol MCP Server, which means it retrieves data without modifying state.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for get_library_toc: 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 DM20 Protocol. Nothing to install.
get_library_toc 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_library_toc 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_library_toc. 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_library_toc is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). 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 →