AI agents use create_note_tool to create or update resources in Alaya — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alaya environment.
This tool creates new notes in a personal knowledge vault. Creation is a reversible write operation—notes can be deleted or modified later. It poses medium severity risk: an agent could create many notes, pollute the knowledge base, or create misleading/false information, but the effects are not irreversible (notes can be deleted) and do not involve code execution or financial impact.
From the tool's definition Tool name 'create_note_tool' indicates note creation. Server description states the system enables 'full read, write, search, and synthesis operations on notes.' Sibling tools include 'delete_note_tool' and 'append_to_note_tool', confirming this server…
Attacks that exploit this kind of access
create_note_tool. It is categorised as a Write tool in the Alaya MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alaya MCP server in PolicyLayer and add a rule for create_note_tool: 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 Alaya. Nothing to install.
create_note_tool 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_tool 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_tool. 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_tool is provided by the Alaya MCP server (luke-kucing/alaya). 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 →