AI agents call getNoteHistory to retrieve information from Memnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves historical versions of notes without modifying, deleting, or executing any operations. It is a pure read operation that queries archived note data. The blast radius of misuse is minimal—an agent could only access historical note information it may not be authorized to see, which is a confidentiality concern but not a destructive or operational risk.
From the tool's definition Tool name 'getNoteHistory' and description 'Get note history' and 'Returns all archived versions of the note' clearly indicate data retrieval with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get note history Returns all archived versions of the note, newest first. A version is archived automatically on every PUT. It is categorised as a Read tool in the Memnote MCP Server, which means it retrieves data without modifying state.
getNoteHistory accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Memnote MCP server in PolicyLayer and add a rule for getNoteHistory: 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 Memnote. Nothing to install.
getNoteHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getNoteHistory 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 getNoteHistory. 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.
getNoteHistory is provided by the Memnote MCP server (@randomfact/memnote-mcp-server). 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 →