AI agents call list_books to retrieve information from Tilnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata about books without creating, modifying, or deleting any data. It has no side effects and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'list_books' and description 'List your Tilnote books. Returns title, page count, and URL for each book' indicate retrieval of existing data with no modification.
Attacks that exploit this kind of access
List your Tilnote books. Returns title, page count, and URL for each book. It is categorised as a Read tool in the Tilnote MCP Server, which means it retrieves data without modifying state.
Register the Tilnote MCP server in PolicyLayer and add a rule for list_books: 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 Tilnote. Nothing to install.
list_books 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_books 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_books. 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_books is provided by the Tilnote MCP server (wisdomcrane/tilnote-mcp-server). 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 →