add_label_to_note
AI agents use add_label_to_note to create or update resources in NotesKeep MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NotesKeep MCP Server environment.
Adding a label to a note is a write operation that modifies data (note metadata) reversibly. It does not delete, execute code, or move money. The empty description slightly lowers confidence, but the tool name and sibling context provide sufficient clarity. Severity is medium because mislabeling notes has limited blast radius—it degrades organization but does not cause data loss or irreversible damage.
From the tool's definition Tool name 'add_label_to_note' indicates modifying note metadata by adding labels. Sibling tools include 'create_label' and 'delete_label', confirming this server manages note organization.
Attacks that exploit this kind of access
add_label_to_note. It is categorised as a Write tool in the NotesKeep MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NotesKeep MCP Server MCP server in PolicyLayer and add a rule for add_label_to_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 NotesKeep MCP Server. Nothing to install.
add_label_to_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 add_label_to_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 add_label_to_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.
add_label_to_note is provided by the NotesKeep MCP Server MCP server (mariomosca/noteskeep-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 →