AI agents call check_match_status to retrieve information from MCP Arena without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays information about match status and a URL without modifying, executing, or deleting anything. It is purely informational, similar to 'get_arena_state' on the same server. The blast radius of misuse is minimal (information disclosure only). Low severity because displaying a URL or match status poses no operational risk to the arena or user data.
From the tool's definition Tool description states 'Verificar si se encontro oponente' (verify if an opponent was found) and 'MUESTRA LA URL' (show the URL to user). This is a status check operation with no side effects—it queries match state and displays information.
Attacks that exploit this kind of access
Verificar si se encontro oponente. Cuando lo encuentre MUESTRA LA URL al usuario. It is categorised as a Read tool in the MCP Arena MCP Server, which means it retrieves data without modifying state.
Register the MCP Arena MCP server in PolicyLayer and add a rule for check_match_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 MCP Arena. Nothing to install.
check_match_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 check_match_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 check_match_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.
check_match_status is provided by the MCP Arena MCP server (jerick97/mcp-arena). 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 →