AI agents call audible_search_library to retrieve information from Audible 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 library metadata (title, ASIN, author, narrator, series) without creating, modifying, or deleting any data. It performs read-only operations on the user's Audible library. The low severity reflects minimal blast radius—worst case an agent retrieves unauthorized library information, but cannot alter or delete anything.
From the tool's definition Tool description states it "Search[es] the authenticated library" using "client-side filtering". The verb "search" combined with "retrieval" focus in server description indicates data querying with no side effects.
Attacks that exploit this kind of access
Search the authenticated library by title, ASIN, author, narrator, or series name using client-side filtering across the first few pages. It is categorised as a Read tool in the Audible MCP Server, which means it retrieves data without modifying state.
Register the Audible MCP server in PolicyLayer and add a rule for audible_search_library: 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 Audible. Nothing to install.
audible_search_library 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 audible_search_library 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 audible_search_library. 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.
audible_search_library is provided by the Audible MCP server (tannerwj/audible-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 →