List local note IDs and titles.
AI agents call list_notes to retrieve information from Local Knowledge Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves metadata (IDs and titles) from existing notes without creating, modifying, deleting, or executing any operations. It is a straightforward read/list operation with minimal security risk. The low severity reflects that exposure of note IDs and titles poses minimal harm in most contexts.
From the tool's definition Tool name is 'list_notes' and description states 'List local note IDs and titles' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List local note IDs and titles. It is categorised as a Read tool in the Local Knowledge Desk MCP Server, which means it retrieves data without modifying state.
Register the Local Knowledge Desk 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 Local Knowledge Desk. 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 Local Knowledge Desk MCP server (matiaslaukka/openai-mcp-project). 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 →