This record as markdown: /tools/io-github-portel-dev-ncp/list-recordings.md
What list_recordings does on Ncp
AI agents call list_recordings to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_recordings is rated Low
This tool queries and returns meeting recordings without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves data from a system, consistent with the Read category which encompasses search, list, get, and fetch operations.
From the tool's definition Tool name 'list_recordings' and description 'List meeting recordings' indicate a retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs list_recordings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_recordings, this is the rule to start with:
list_recordings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every list_recordings call is checked against it from then on.
Questions about list_recordings
List meeting recordings. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue