List notes with optional filtering and search capabilities
AI agents call list_notes to retrieve information from Sidvy 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/queries existing notes using optional filters and search—classic Read operation. No side effects, no data mutation, no code execution. The filtering and search parameters are read-only operations. Severity is low because the impact of misuse is limited to unauthorized information disclosure within the note-taking system.
From the tool's definition Tool name 'list_notes' and description 'List notes with optional filtering and search capabilities' indicate retrieval of note data without modification. No mention of creation, deletion, or execution.
Attacks that exploit this kind of access
List notes with optional filtering and search capabilities. It is categorised as a Read tool in the Sidvy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for list_notes: 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 Sidvy MCP Server. Nothing to install.
list_notes 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_notes 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_notes. 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_notes is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-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 →