キーと値のペアでメモを保存します
AI agents use save_note to create or update resources in NestJS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NestJS MCP Server environment.
This tool creates or updates notes in storage, fitting the Write category (creates/modifies data reversibly). The severity is medium because misuse could result in modified note data, but notes are typically low-risk compared to financial or system-critical data. Given the NestJS/DDD context suggesting a note management system, this appears to be application-level data modification without destructive capability.
From the tool's definition Tool description indicates 'save_note' saves key-value pair memos. The verb 'saves' and the functional context of persisting data to storage demonstrates a write operation that creates or modifies data reversibly.
Attacks that exploit this kind of access
キーと値のペアでメモを保存します. It is categorised as a Write tool in the NestJS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NestJS MCP Server MCP server in PolicyLayer and add a rule for save_note: 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.
save_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_note 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 save_note. 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.
save_note 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 →