today_rhythm
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 今天节奏怎么样 / 今天势能怎么样 / 今天干支是什么 / 今天适不适合签约开会发版 / 今天流通怎么样 / 该不该推进某事 / what is today's rhythm. Returns east pillars, this month’s fold year (same pillar), month post...
This record as markdown: /tools/balance-engine-mcp/today-rhythm.md
What today_rhythm does on Balance Engine
AI agents call today_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 申 / 未时. Adds the public hour pillar. Use when the user says 现在 / 下午 / 几点. |
locale | string | — | Reply language. zh (default) or en. |
Parameters from the server's own tool schema.
Why today_rhythm is rated Low
Without any rule in front of it, every call an agent makes to today_rhythm happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs today_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 today_rhythm, this is the rule to start with:
today_rhythm gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Balance Engine, apply this rule, and every today_rhythm call is checked against it from then on.
Questions about today_rhythm
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 今天节奏怎么样 / 今天势能怎么样 / 今天干支是什么 / 今天适不适合签约开会发版 / 今天流通怎么样 / 该不该推进某事 / what is today's rhythm. Returns east pillars, this month’s fold year (same pillar), month posture × west tightness as do/don't, plus the daily west almanac. Always surface the fold-year line and ask what they lived that year. 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.
today_rhythm accepts 3 parameters: date, hour, locale. The full parameter table on this page comes from the server's own tool schema.
Register the Balance Engine MCP server in PolicyLayer and add a rule for today_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.
today_rhythm is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the today_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.
Set action: deny in the PolicyLayer policy for today_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.
today_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.
More on Balance Engine, and thousands of servers like it.
This server
Across the catalogue