get_note_by_name
AI agents call get_note_by_name to retrieve information from Amplenote Cache MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a note by its name from the Amplenote SQLite cache. It performs a lookup/fetch operation with no side effects—it does not modify, delete, or execute arbitrary code. The empty description reduces confidence slightly, but the clear naming pattern and sibling tool context confirm this is a simple read operation against cached note data.
From the tool's definition Tool name 'get_note_by_name' and sibling tools ('get_note_by_uuid', 'get_note_references', 'list_notes', 'search_notes') are all retrieval operations. Server description emphasizes 'search and retrieval of notes' with 'no write/delete capabilities mentioned'.
Attacks that exploit this kind of access
get_note_by_name. It is categorised as a Read tool in the Amplenote Cache MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amplenote Cache MCP Server MCP server in PolicyLayer and add a rule for get_note_by_name: 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 Amplenote Cache MCP Server. Nothing to install.
get_note_by_name 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 get_note_by_name 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 get_note_by_name. 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.
get_note_by_name is provided by the Amplenote Cache MCP Server MCP server (mikekwright/amplenote-cache-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 →