AI agents call get_note 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.
This tool only retrieves (reads) user notes associated with a LeetCode problem. It performs a data retrieval operation with no capability to modify, delete, or execute actions. The authentication requirement does not change the classification as it is a standard access control mechanism. The operation is non-destructive and has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_note' and description states it 'Retrieves user notes' — a read-only operation that queries and returns existing data without modification or side effects.
Attacks that exploit this kind of access
Retrieves user notes for a specific LeetCode problem by its question ID, returning the complete note content and metadata (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 get_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 Leetcode. Nothing to install.
get_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_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_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_note 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 →