Create a new local Markdown note without overwriting an existing note.
AI agents use create_note to create or update resources in Local Knowledge Desk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Knowledge Desk environment.
This tool creates new data (Markdown notes) in the local knowledge base, which is a Write operation. Severity is medium because misuse could result in storage of unwanted data or information disclosure if sensitive notes are created, but the operation is reversible through the delete_note tool also available on this server.
From the tool's definition Tool description states 'Create a new local Markdown note' which is a data creation operation. The clarification 'without overwriting an existing note' confirms it is reversible (notes can be deleted).
Attacks that exploit this kind of access
Create a new local Markdown note without overwriting an existing note. It is categorised as a Write tool in the Local Knowledge Desk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Local Knowledge Desk MCP server in PolicyLayer and add a rule for create_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 Local Knowledge Desk. Nothing to install.
create_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 create_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 create_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.
create_note 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 →