get_note_references
AI agents call get_note_references 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 reference data about notes (likely bidirectional links mentioned in server description) with no side effects. It is a data retrieval operation analogous to the other read-only tools on this server. Empty description slightly lowers confidence but context strongly suggests read-only semantics.
From the tool's definition Tool name is 'get_note_references' and resides on Amplenote Cache MCP Server which provides 'search and retrieval of notes and tasks' with no write/delete capabilities mentioned.
Attacks that exploit this kind of access
get_note_references. 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_references: 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_references 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_references 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_references. 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_references 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 →