query_tasks
AI agents call query_tasks 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.
The tool name 'query_tasks' suggests a read/search operation consistent with the server's stated purpose of search and retrieval. Sibling tools are all read-oriented (get, list, search). However, the description is empty, which lowers confidence. If 'query' implies arbitrary SQL execution, it could be Execute or Destructive, but context strongly suggests it is a read operation for task retrieval.
From the tool's definition Tool name is 'query_tasks'; server description mentions 'search and retrieval of notes and tasks, including full-text search, bidirectional references, task filtering by priority and due dates'; sibling tools include list_tasks, search_tasks suggesting…
Attacks that exploit this kind of access
query_tasks. 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 query_tasks: 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.
query_tasks 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 query_tasks 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 query_tasks. 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.
query_tasks 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.
query_tasks is one line of Amplenote Cache MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →