Create a new note.
AI agents use create_note to create or update resources in Rhizm MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rhizm MCP Server environment.
Creating a note is a Write operation—it adds new data to the system reversibly. If created in error, notes can be deleted (delete_task exists as a sibling tool, suggesting parallel deletion capability). The blast radius is low: a mistaken note cannot cause financial loss, execute code, or destroy critical data. Severity is low because notes are typically non-critical information storage.
From the tool's definition Tool name 'create_note' and description 'Create a new note' indicate data creation. The server context confirms this is a note management tool that creates new entries via API integration.
Attacks that exploit this kind of access
Create a new note. It is categorised as a Write tool in the Rhizm MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rhizm MCP Server 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 Rhizm MCP Server. 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 Rhizm MCP Server MCP server (rhizmapp/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 →