energy_adjust
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 能量怎么调 / 个人今天该推还是该收 / 团队这周该不该硬上线 / personal vs company rhythm. Same engine, two seats: personal (sleep/load) or org (window push vs hold). Not HR scoring, not m...
This record as markdown: /tools/balance-engine-mcp/energy-adjust.md
What energy_adjust does on Balance Engine
AI agents call energy_adjust 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 | — | Optional hour for the personal seat (HH:MM or 时支). |
seat | string | — | personal (default) = body load/sleep. org = team window, push vs hold. |
month | string | — | Month YYYY-MM for the org seat. Default: current month. |
locale | string | — | Reply language. zh (default) or en. |
Parameters from the server's own tool schema.
Why energy_adjust is rated Low
Without any rule in front of it, every call an agent makes to energy_adjust 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 energy_adjust 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 energy_adjust, this is the rule to start with:
energy_adjust 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 energy_adjust call is checked against it from then on.
Questions about energy_adjust
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 能量怎么调 / 个人今天该推还是该收 / 团队这周该不该硬上线 / personal vs company rhythm. Same engine, two seats: personal (sleep/load) or org (window push vs hold). Not HR scoring, not medical treatment. 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.
energy_adjust accepts 5 parameters: date, hour, seat, month, 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 energy_adjust: 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.
energy_adjust 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 energy_adjust 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 energy_adjust. 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.
energy_adjust 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