Registers a new demo://note/N resource and notifies list_changed.
AI agents use add_note to create or update resources in MCP from Scratch Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP from Scratch Server environment.
The tool creates or registers a new note resource, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The notification side effect (list_changed) is a normal consequence of the write action.
From the tool's definition Tool description states it 'Registers a new demo://note/N resource', which is a create operation that adds a new note resource to the system.
Documented attack patterns abuse exactly the kind of access add_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP from Scratch Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_note:
{
"version": "1",
"default": "deny",
"tools": {
"add_note": {
"limits": [
{
"counter": "add_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_note 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.
Free to start. No card required.
Registers a new demo://note/N resource and notifies list_changed. It is categorised as a Write tool in the MCP from Scratch Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP from Scratch Server MCP server in PolicyLayer and add a rule for add_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 MCP from Scratch Server. Nothing to install.
add_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 add_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 add_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.
add_note is provided by the MCP from Scratch Server MCP server (pguso/mcp-from-scratch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP from Scratch Server, 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.
12 MCP from Scratch Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.