get_tasks_by_note
AI agents call get_tasks_by_note 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 tasks linked to a specific note from the Amplenote cache. It has no side effects—it only reads and returns data without creating, modifying, deleting, or executing arbitrary code. The blast radius of misuse is minimal: an agent could retrieve unwanted task information but cannot alter the database or trigger external operations.
From the tool's definition Tool name 'get_tasks_by_note' combined with sibling tools (list_notes, list_tasks, query_tasks, search_notes, search_tasks) and server description stating it provides 'access to...SQLite database cache, enabling search and retrieval of notes and tasks'…
Attacks that exploit this kind of access
get_tasks_by_note. 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_tasks_by_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 Amplenote Cache MCP Server. Nothing to install.
get_tasks_by_note 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_tasks_by_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 get_tasks_by_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.
get_tasks_by_note 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 →