AI agents call audible_get_auth_status 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 queries and retrieves local authentication metadata—a read-only operation with no side effects. It does not create, modify, delete, execute code, or involve financial transactions. While auth metadata could be sensitive, the tool itself only retrieves existing state without enabling further privileged actions on its own.
From the tool's definition Tool name 'audible_get_auth_status' and description 'Return local auth metadata for the configured Audible device registration' indicate retrieval of authentication state without modification or execution.
Attacks that exploit this kind of access
Return local auth metadata for the configured Audible device registration. 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_auth_status: 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_auth_status 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_auth_status 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_auth_status. 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_auth_status 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 →