List call recordings on this account. Optionally filter by CallSid, or by DateCreated range. Returns Twilio
AI agents call list_recordings to retrieve information from Mcp Ap2 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 existing call recording metadata without modifying, executing, or destroying any data. The optional filters (CallSid, DateCreated range) are typical of read-only list operations. The low severity reflects minimal blast radius—an AI agent misusing this would only gain unauthorized access to metadata about call recordings, not cause irreversible damage or financial impact.
From the tool's definition Tool name 'list_recordings' and description 'List call recordings on this account' clearly indicate data retrieval with optional filtering parameters. No creation, modification, deletion, or execution of external systems occurs.
Documented attack patterns abuse exactly the kind of access list_recordings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for list_recordings:
{
"version": "1",
"default": "deny",
"tools": {
"list_recordings": {}
}
}list_recordings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List call recordings on this account. Optionally filter by CallSid, or by DateCreated range. Returns Twilio. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for list_recordings: 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 Mcp Ap2. Nothing to install.
list_recordings 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 list_recordings 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 list_recordings. 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.
list_recordings is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.