# ss_clear_schedule

A destructive tool on the Ultra MCP-SS MCP server.

Agent View of the PolicyLayer registry record for `ss_clear_schedule`. HTML page: https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-clear-schedule

## Facts

- Tool: `ss_clear_schedule`
- Server: Ultra MCP-SS (`motebus/ultra-mcp-ss`) — https://policylayer.com/tools/motebus-ultra-mcp-ss.md
- Homepage: https://github.com/motebus/ultra-mcp-ss
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why ss_clear_schedule is rated Critical

An AI agent that decides to call ss_clear_schedule doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ultra MCP-SS is gone. There is no undo for destructive operations.

## Use case

AI agents call ss_clear_schedule to permanently remove resources in Ultra MCP-SS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Ultra MCP-SS:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ss_clear_schedule"
  ]
}
```

## Other tools on Ultra MCP-SS (17)

- `ss_clear` — Destructive — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-clear.md
- `ss_drop` — Destructive — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-drop.md
- `ss_command` — Execute — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-command.md
- `ss_go` — Execute — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-go.md
- `ss_app` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-app.md
- `ss_default` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-default.md
- `ss_dj` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-dj.md
- `ss_frame` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-frame.md
- `ss_help` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-help.md
- `ss_home` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-home.md
- `ss_html` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-html.md
- `ss_marquee` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-marquee.md
- `ss_notify` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-notify.md
- `ss_text` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-text.md
- `ss_toast` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-toast.md
- `ss_touch` — Other — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-touch.md
- `ss_status` — Read — https://policylayer.com/tools/motebus-ultra-mcp-ss/ss-status.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=motebus-ultra-mcp-ss · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/motebus-ultra-mcp-ss