Medium Risk

create_note_tool

create_note_tool

How to control create_note_tool ↓

What create_note_tool does on Brain

AI agents use create_note_tool to create or update resources in Brain — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brain environment.

Medium Risk

Why create_note_tool needs a policy

A tool that creates notes in a private Markdown knowledge base creates or modifies data reversibly. It poses minimal blast radius since notes can be edited or deleted, making it a Write category tool with low severity. Confidence reduced slightly due to absent description, but context from server purpose and sibling tools is clear.

From the tool's definition Tool name 'create_note_tool' indicates note creation. Server description states 'read/write tools for MCP-compatible AI clients' and explicitly mentions write capability.

Documented attack patterns abuse exactly the kind of access create_note_tool gives an agent:

How to control create_note_tool

PolicyLayer is an MCP gateway — it sits between your AI agents and Brain, and nothing reaches the server without passing your rules. This is the rule we recommend for create_note_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_note_tool": {
      "limits": [
        {
          "counter": "create_note_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_note_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Brain — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_note_tool

What does the create_note_tool tool do? +

create_note_tool. It is categorised as a Write tool in the Brain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_note_tool? +

Register the Brain 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 Brain. Nothing to install.

What risk level is create_note_tool? +

create_note_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_note_tool? +

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.

How do I block create_note_tool completely? +

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.

What MCP server provides create_note_tool? +

create_note_tool is provided by the Brain MCP server (irahulstomar/brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Brain tool call.

Start from Brain, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 Brain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.