# get_upcoming_ctfs

Retrieve upcoming CTF events from CTFtime.org.

Agent View of the PolicyLayer registry record for `get_upcoming_ctfs`. HTML page: https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-upcoming-ctfs

## Facts

- Tool: `get_upcoming_ctfs`
- Server: CTFtime MCP Server (`0x-professor/ctf-time-mcp`) — https://policylayer.com/tools/0x-professor-ctf-time-mcp.md
- Homepage: https://github.com/0x-Professor/CTF-time-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_upcoming_ctfs",
    "arguments": {}
  }
}
```

## Why get_upcoming_ctfs is rated Low

This tool performs a retrieval/query operation on public CTF event data. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. The blast radius is minimal—an AI agent cannot misuse this tool to cause harm beyond potentially excessive API calls or information gathering about public CTF events.

From the tool's own definition: "Tool name 'get_upcoming_ctfs' and description 'Retrieve upcoming CTF events from CTFtime.org' indicate a read-only query operation that retrieves publicly available competition schedule data with no modification, deletion, or execution of external operations."

## Use case

AI agents call get_upcoming_ctfs to retrieve information from CTFtime MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches CTFtime MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_upcoming_ctfs": {}
  }
}
```

## Other tools on CTFtime MCP Server (8)

- `get_ctf_calendar` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-ctf-calendar.md
- `get_event_details` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-event-details.md
- `get_event_results` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-event-results.md
- `get_past_ctfs` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-past-ctfs.md
- `get_team_info` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-team-info.md
- `get_top_teams` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-top-teams.md
- `get_top_teams_by_country` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-top-teams-by-country.md
- `search_events` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/search-events.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0x-professor-ctf-time-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x-professor-ctf-time-mcp