# list_teams

List and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count.

Agent View of the PolicyLayer registry record for `list_teams`. HTML page: https://policylayer.com/tools/com-oneuptime-mcp/list-teams

## Facts

- Tool: `list_teams`
- Server: OneUptime (`https://oneuptime.com/mcp`) — https://policylayer.com/tools/com-oneuptime-mcp.md
- Homepage: https://github.com/OneUptime/oneuptime
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 5
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `skip` | number | no | Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record. |
| `sort` | object | no | Sort order for results. Use "ASC" for ascending or "DESC" for descending. Example: {"createdAt": "DESC"} to sort by newest first. |
| `limit` | number | no | Maximum number of records to return. Default: 10, Maximum: 100. |
| `query` | object | no | Filter criteria for Teams. Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotE |
| `select` | array | no | Optional: field names to return for each Team (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if n |

Parameters from the server's own tool schema.

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

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

## Why list_teams is rated Low

Even though list_teams only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: High parameter count (36 properties)

## Use case

AI agents call list_teams to retrieve information from OneUptime 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 OneUptime:

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

## Other tools on OneUptime (222)

- `delete_alert` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert.md
- `delete_alert_internal_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-internal-note.md
- `delete_alert_severity` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-severity.md
- `delete_alert_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-state.md
- `delete_alert_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-state-timeline.md
- `delete_incident` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident.md
- `delete_incident_alert` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-alert.md
- `delete_incident_internal_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-internal-note.md
- `delete_incident_public_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-public-note.md
- `delete_incident_severity` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-severity.md
- `delete_incident_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-state.md
- `delete_incident_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-state-timeline.md
- `delete_label` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-label.md
- `delete_monitor` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor.md
- `delete_monitor_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor-status.md
- `delete_monitor_status_event` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor-status-event.md
- `delete_on_call_policy` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-on-call-policy.md
- `delete_postmortem_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-postmortem-status.md
- `delete_scheduled_maintenance_event` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-event.md
- `delete_scheduled_maintenance_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-state.md
- `delete_scheduled_maintenance_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-state-timeline.md
- `delete_security_case` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case.md
- `delete_security_case_evidence` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-evidence.md
- `delete_security_case_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-note.md
- `delete_security_case_priority` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-priority.md
- `delete_security_case_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-status.md
- `delete_security_case_task` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-task.md
- `delete_security_detection` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-detection.md
- `delete_security_playbook` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-playbook.md
- `delete_status_page` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-status-page.md
- …and 192 more: https://policylayer.com/tools/com-oneuptime-mcp.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=com-oneuptime-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-oneuptime-mcp