# search_events

A read tool on the CTFtime MCP Server MCP server.

Agent View of the PolicyLayer registry record for `search_events`. HTML page: https://policylayer.com/tools/0x-professor-ctf-time-mcp/search-events

## Facts

- Tool: `search_events`
- 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": "search_events",
    "arguments": {}
  }
}
```

## Why search_events is rated Low

This tool searches and retrieves information about CTF events from CTFtime.org. It follows the established pattern of read-only data access seen across all sibling tools. There is no indication of data modification, deletion, code execution, or financial operations. The primary function is information retrieval, which carries minimal risk of misuse.

From the tool's own definition: "Tool name 'search_events' combined with server description stating it 'enables users to search for upcoming events' and 'retrieve information about CTF competitions'. Sibling tools are all read-only retrieval operations (get_* pattern)."

## Use case

AI agents call search_events 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": {
    "search_events": {}
  }
}
```

## 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
- `get_upcoming_ctfs` — Read — https://policylayer.com/tools/0x-professor-ctf-time-mcp/get-upcoming-ctfs.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