AI agents call query_notes to retrieve information from Tick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches notes within specified scopes (folder/project). It performs read-only operations analogous to grep searching. There are no side effects, data modifications, or destructive actions. It represents a classic Read operation with minimal risk if misused by an AI agent—worst case being exposure of note content the agent shouldn't access, but not data loss or external effects.
From the tool's definition Tool name 'query_notes' and description explicitly states 'Query notes' with 'content search' capabilities. The verb 'query' combined with 'search' indicates data retrieval without modification.
Attacks that exploit this kind of access
Query notes with folder/project scope and grep-like content search. It is categorised as a Read tool in the Tick MCP Server, which means it retrieves data without modifying state.
Register the Tick MCP server in PolicyLayer and add a rule for query_notes: 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 Tick. Nothing to install.
query_notes 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_notes 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_notes. 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_notes is provided by the Tick MCP server (kpihx/tick-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 →