保存されているすべてのメモのキーを一覧表示します
AI agents call list_notes to retrieve information from NestJS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The list_notes tool retrieves and displays information about existing notes. It performs no write operations, does not execute code, does not delete data, and does not involve financial transactions. The operation is read-only and has minimal blast radius even if invoked incorrectly by an AI agent, as it only returns a list of note identifiers.
From the tool's definition The tool description states it lists keys of all saved notes ("保存されているすべてのメモのキーを一覧表示します" - "list the keys of all saved notes"). This is a retrieval/query operation that returns data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
保存されているすべてのメモのキーを一覧表示します. It is categorised as a Read tool in the NestJS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NestJS 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 NestJS 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 NestJS MCP Server MCP server (kaz29/mcp-server-example). 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 →