AI agents call audible_get_content_metadata 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 metadata and chapter data from Audible for a given ASIN. It performs no creation, modification, deletion, or execution of external operations. The blast radius of misuse is minimal — an attacker could enumerate or exfiltrate metadata, but cannot alter user data, trigger payments, or execute code. Classified as Read with low severity.
From the tool's definition Tool name contains 'get' and description states 'Fetch content metadata' and 'including chapter information' — purely retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Fetch content metadata for an Audible ASIN, including chapter information. 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_get_content_metadata: 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_get_content_metadata 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_get_content_metadata 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_get_content_metadata. 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_get_content_metadata 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 →