AI agents call toc to retrieve information from Tome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'toc' most likely stands for 'table of contents', which is a read operation to retrieve structured document metadata. Given the server context (research paper library), this likely fetches the TOC of a paper or the library. However, the empty description significantly lowers confidence. No evidence of write, execute, or destructive behavior.
From the tool's definition Tool name 'toc' suggests Table of Contents retrieval; description is empty and uninformative.
Attacks that exploit this kind of access
toc. It is categorised as a Read tool in the Tome MCP Server, which means it retrieves data without modifying state.
Register the Tome MCP server in PolicyLayer and add a rule for 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 Tome. Nothing to install.
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 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 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.
toc is provided by the Tome MCP server (retospect/tome-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 →