Get all recordings with a specific tag/folder.
AI agents call get_recordings_by_tag to retrieve information from Plaud Notes 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 and filters recordings by tag/folder metadata—a read-only query operation with no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is limited to unauthorized access to existing voice recordings and their metadata.
From the tool's definition Tool description: 'Get all recordings with a specific tag/folder.' The verb 'Get' and context of querying existing recordings indicate retrieval without modification.
Attacks that exploit this kind of access
Get all recordings with a specific tag/folder. It is categorised as a Read tool in the Plaud Notes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Plaud Notes MCP Server MCP server in PolicyLayer and add a rule for get_recordings_by_tag: 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 Plaud Notes MCP Server. Nothing to install.
get_recordings_by_tag 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_recordings_by_tag 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_recordings_by_tag. 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_recordings_by_tag is provided by the Plaud Notes MCP Server MCP server (jameshenning/plaudnotes). 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 →