body_rhythm

SERVERBalance Engine SOURCEbalance-engine-mcp

Low RISK CLASS

Category Other

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/balance-engine-mcp/body-rhythm.md

WHAT IT DOES

What body_rhythm does on Balance Engine

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

Parameter	Type	Required	Description
`date`	string	—	Date YYYY-MM-DD. Default: today in Asia/Shanghai. Use when the user asks about a specific day.
`hour`	string	—	Clock HH:MM or 时支 like 申. Pins the hour slot. Use when the user says 现在 / 下午 / 几点.
`locale`	string	—	Reply language. zh (default) or en.

Parameters from the server's own tool schema.

RISK

Why body_rhythm is rated Low

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs body_rhythm safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Balance Engine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For body_rhythm, this is the rule to start with:

body_rhythm Rate-limited

body_rhythm gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "body_rhythm": {
      "limits": [
        {
          "counter": "body_rhythm_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Balance Engine, apply this rule, and every body_rhythm call is checked against it from then on.

FAQ

Questions about body_rhythm

What does the body_rhythm tool do? +

This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 今晚要不要提前睡 / 今天该不该加练 / 现在这个时辰适不适合动 / body energy / train or rest. Public body-energy rehearsal from solar term + hour + month posture × sky tightness. Not a diagnosis. Adjust ≠ infuse energy. Public · local · no API key. Preview ≠ prediction. It is categorised as a Other tool in the Balance Engine MCP Server, which means it performs auxiliary operations.

What parameters does body_rhythm accept? +

body_rhythm accepts 3 parameters: date, hour, locale. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on body_rhythm? +

Register the Balance Engine MCP server in PolicyLayer and add a rule for body_rhythm: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Balance Engine. Nothing to install.

What risk level is body_rhythm? +

body_rhythm is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit body_rhythm? +

Yes. Add a rate_limit block to the body_rhythm rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block body_rhythm completely? +

Set action: deny in the PolicyLayer policy for body_rhythm. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides body_rhythm? +

body_rhythm is provided by the Balance Engine MCP server (balance-engine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Balance Engine, and thousands of servers like it.

This server

All 9 Balance Engine tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →