Update the notes field for the current user WHAT: Updates the notes/metadata field for the authenticated user. WHEN TO USE: 1. When the user wants to store personal preferences or context 2. When you need to persist user-specific information for future conversations 3. When updating user metadata...
AI agents use update_user_notes to create or update resources in Forgetful — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgetful environment.
This tool modifies user data (notes/metadata field) but does so reversibly and without destructive effects. It does not delete data, execute code, or move money. The 'notes' field is user-specific metadata that can be changed, deleted, or overwritten later, making it a Write operation rather than Destructive.
From the tool's definition Tool description states 'Updates the notes field for the current user' and 'Updates only the notes field for the current user'. This is a modification operation that creates or alters user metadata reversibly.
Documented attack patterns abuse exactly the kind of access update_user_notes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for update_user_notes:
{
"version": "1",
"default": "deny",
"tools": {
"update_user_notes": {
"limits": [
{
"counter": "update_user_notes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_user_notes 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.
Update the notes field for the current user WHAT: Updates the notes/metadata field for the authenticated user. WHEN TO USE: 1. When the user wants to store personal preferences or context 2. When you need to persist user-specific information for future conversations 3. When updating user metadata that doesn't fit other structured fields BEHAVIOR: - Updates only the 'notes' field for the current user - Returns the updated User object with new notes value - Does not modify other user fields (name, email, etc.) - Auto-creates user if they don't exist - Replaces existing value of notes field so remember to pass persist if still relevant WHEN NOT TO USE: - When you need to update other user fields (name, email) - those are managed by IDP - When notes haven't actually changed - For storing temporary conversation context (use memory system instead) Args: user_notes: The new notes content to store for the user ctx: FastMCP Context (automatically injected). It is categorised as a Write tool in the Forgetful MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgetful MCP server in PolicyLayer and add a rule for update_user_notes: 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 Forgetful. Nothing to install.
update_user_notes 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 update_user_notes 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 update_user_notes. 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.
update_user_notes is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.