# activity_window

This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 今天什么时候适合运动 / 今天哪个时辰适合深工 / 什么时候开会 / 什么时候练 / 什么时候发版 / 什么时候该休息 / activity window / when to exercise. Maps month posture × twelve hours × body load to 2–3 clock windows for task=deep_work|train|meet|ship|rest. Windows are suggested slots, not a guarantee. Not meds, not glucose, not a diagnosis. Public · local · no API key. Preview ≠ prediction.

Agent View of the PolicyLayer registry record for `activity_window`. HTML page: https://policylayer.com/tools/balance-engine-mcp/activity-window

## Facts

- Tool: `activity_window`
- Server: Balance Engine (`balance-engine-mcp`) — https://policylayer.com/tools/balance-engine-mcp.md
- Install: `npx -y balance-engine-mcp`
- Homepage: https://www.npmjs.com/package/balance-engine-mcp
- Risk category: Other (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `date` | string | no | Date YYYY-MM-DD. Default: today in Asia/Shanghai. Use when the user asks about a specific day. |
| `task` | string | no | What to place: deep_work (default), train, meet, ship, rest. |
| `locale` | string | no | Reply language. zh (default) or en. |

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

## Why activity_window is rated Low

Without any rule in front of it, every call an agent makes to activity_window happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

## Use case

AI agents call activity_window as a supporting operation in Balance Engine workflows.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Balance Engine:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "activity_window": {
      "limits": [
        {
          "counter": "activity_window_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Balance Engine (8)

- `month_brief` — Destructive — https://policylayer.com/tools/balance-engine-mcp/month-brief.md
- `body_rhythm` — Other — https://policylayer.com/tools/balance-engine-mcp/body-rhythm.md
- `energy_adjust` — Other — https://policylayer.com/tools/balance-engine-mcp/energy-adjust.md
- `personal_day` — Other — https://policylayer.com/tools/balance-engine-mcp/personal-day.md
- `personal_month` — Other — https://policylayer.com/tools/balance-engine-mcp/personal-month.md
- `time_fold` — Other — https://policylayer.com/tools/balance-engine-mcp/time-fold.md
- `today_rhythm` — Other — https://policylayer.com/tools/balance-engine-mcp/today-rhythm.md
- `sky_window` — Read — https://policylayer.com/tools/balance-engine-mcp/sky-window.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=balance-engine-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/balance-engine-mcp