AI agents call search_notes to retrieve information from Leetcode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query operation that retrieves existing user notes and associated problem information. The word 'searches' and 'returning' confirm this is a read-only operation. Despite requiring authentication, it does not create, modify, delete, or execute any external operations—it only accesses and returns data. This aligns with the Read category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool name 'search_notes' and description 'Searches for user notes on LeetCode...returning note content' indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Searches for user notes on LeetCode with filtering options, returning note content and associated problem information (requires authentication). It is categorised as a Read tool in the Leetcode MCP Server, which means it retrieves data without modifying state.
Register the Leetcode MCP server in PolicyLayer and add a rule for search_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 Leetcode. Nothing to install.
search_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 search_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 search_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.
search_notes is provided by the Leetcode MCP server (@jinzcdev/leetcode-mcp-server). 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 →