AI agents call get_recent_ac_submissions 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 retrieves user submission data without creating, modifying, deleting, or executing any operations. It is purely informational/read-only. The incomplete description ('Retrieves a user') is somewhat vague, but the tool name strongly indicates retrieval of AC (accepted) submissions, which aligns with read-only behavior consistent with other tools on this server (get_daily_challenge, get_recent_submissions,…
From the tool's definition Tool name 'get_recent_ac_submissions' and description 'Retrieves a user' indicate data retrieval with no modification. The name suggests fetching accepted submissions, which is a query operation.
Attacks that exploit this kind of access
Retrieves a user. 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_recent_ac_submissions: 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_recent_ac_submissions 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_recent_ac_submissions 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_recent_ac_submissions. 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_recent_ac_submissions 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 →