AI agents call get_problem_submission_report 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 queries and returns data about a LeetCode submission without modifying, deleting, or executing any operations. While it requires authentication and may expose sensitive information (source code of submissions), the action itself is a pure read operation.
From the tool's definition Tool description states it 'Retrieves detailed information about a specific LeetCode submission by its ID, including source code, runtime stats, and test results'.
Attacks that exploit this kind of access
Retrieves detailed information about a specific LeetCode submission by its ID, including source code, runtime stats, and test results (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_problem_submission_report: 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_problem_submission_report 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_problem_submission_report 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_problem_submission_report. 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_problem_submission_report 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 →