Get the status and result of a previously submitted code.
AI agents call get_submission_status to retrieve information from Online Judge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves information about a previously submitted code's status and results. It performs a read-only operation on already-existing data, analogous to checking a test result or submission status in an online judge. There are no modifications, deletions, code execution, or financial implications.
From the tool's definition Tool name is 'get_submission_status' and description states 'Get the status and result of a previously submitted code' - purely retrieval of existing submission data with no side effects.
Attacks that exploit this kind of access
Get the status and result of a previously submitted code. It is categorised as a Read tool in the Online Judge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Online Judge MCP Server MCP server in PolicyLayer and add a rule for get_submission_status: 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 Online Judge MCP Server. Nothing to install.
get_submission_status 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_submission_status 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_submission_status. 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_submission_status is provided by the Online Judge MCP Server MCP server (wangicheng/oj-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 →