month_brief
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 这个月势能怎么样 / 这个月该打磨还是该收 / 这个月哪天发布 / 这个月节奏怎么样 / 流月基调 / 做不做某事 / 哪几天适合上线 / which days to publish. Returns this month’s fold year (same pillar), baseline tone, dated...
This record as markdown: /tools/balance-engine-mcp/month-brief.md
What month_brief does on Balance Engine
AI agents call month_brief to permanently remove resources in Balance Engine, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
month | string | — | Month YYYY-MM. Default: current month. |
locale | string | — | Reply language. zh (default) or en. |
Parameters from the server's own tool schema.
Why month_brief is rated Critical
An AI agent that decides to call month_brief doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Balance Engine is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs month_brief 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 month_brief, this is the rule to start with:
month_brief is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Balance Engine, apply this rule, and every month_brief call is checked against it from then on.
Questions about month_brief
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 这个月势能怎么样 / 这个月该打磨还是该收 / 这个月哪天发布 / 这个月节奏怎么样 / 流月基调 / 做不做某事 / 哪几天适合上线 / which days to publish. Returns this month’s fold year (same pillar), baseline tone, dated sky marks, and a do/drop list. 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 Destructive tool in the Balance Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
month_brief accepts 2 parameters: 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 month_brief: 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.
month_brief is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the month_brief 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 month_brief. 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.
month_brief 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.
Across the catalogue