Get details of a specific recording
AI agents call get_recording to retrieve information from VoIPBin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves recording metadata or details without altering data or triggering actions. However, the severity is elevated to medium rather than low because recordings in VoIP systems may contain sensitive personal information, conversations, or confidential business data. Unauthorized access to recording details could expose such information, making this a moderate information disclosure risk.
From the tool's definition Tool name 'get_recording' and description 'Get details of a specific recording' indicate retrieval of existing data with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get details of a specific recording. It is categorised as a Read tool in the VoIPBin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VoIPBin MCP Server MCP server in PolicyLayer and add a rule for get_recording: 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 VoIPBin MCP Server. Nothing to install.
get_recording 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_recording 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_recording. 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_recording is provided by the VoIPBin MCP Server MCP server (nrjchnd/voipbin-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 →