AI agents call get_audio_info to retrieve information from Claud-Ear without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward metadata retrieval operation. It queries and returns information about audio file properties without any side effects, modification of data, code execution, or destructive actions. It fits the Read category definition: 'retrieves or queries data; no side effects.'
From the tool's definition The tool 'get_audio_info' retrieves 'basic metadata about an audio file (duration, format, sample rate)' with no indication of modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get basic metadata about an audio file (duration, format, sample rate). It is categorised as a Read tool in the Claud-Ear MCP Server, which means it retrieves data without modifying state.
Register the Claud-Ear MCP server in PolicyLayer and add a rule for get_audio_info: 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 Claud-Ear. Nothing to install.
get_audio_info 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 get_audio_info 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 get_audio_info. 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.
get_audio_info is provided by the Claud-Ear MCP server (null-phnix/claud-ear). 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 →