create_label
AI agents use create_label 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.
Creating a label is a Write operation—it adds new metadata to the system reversibly without destructive consequences. Severity is low because labels are organizational metadata with minimal blast radius; misuse would create unwanted labels but cause no data loss or financial impact.
From the tool's definition Tool name 'create_label' and server context showing label management operations (add_label_to_note, delete_label, get_note_labels, list_labels). The tool creates a new label, which is a reversible write operation typical of note-taking systems.
Attacks that exploit this kind of access
create_label. 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 create_label: 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.
create_label 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 create_label 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 create_label. 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.
create_label 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 →