personal_month
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 我这个月怎么样 / 我哪周该推进 / 我这个月适不适合上线 / my month. Personalized flow-month: day-master vs month stem, dated sky, sandbox assumptions, fold-memory prompts. Requires BALA...
This record as markdown: /tools/balance-engine-mcp/personal-month.md
What personal_month does on Balance Engine
AI agents call personal_month as a supporting operation in Balance Engine workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | Optional YYYY-MM-DD to pin which flow month to use. |
birth | object | — | Optional birth profile. If omitted, uses the cloud profile saved on the paid account. |
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 personal_month is rated Low
Without any rule in front of it, every call an agent makes to personal_month happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs personal_month 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 personal_month, this is the rule to start with:
personal_month 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 personal_month call is checked against it from then on.
Questions about personal_month
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 我这个月怎么样 / 我哪周该推进 / 我这个月适不适合上线 / my month. Personalized flow-month: day-master vs month stem, dated sky, sandbox assumptions, fold-memory prompts. Requires BALANCE_API_KEY + birth profile. Empty key → error personal_timetable_requires_key; use free tools instead. Not a fortune verdict. It is categorised as a Other tool in the Balance Engine MCP Server, which means it performs auxiliary operations.
personal_month accepts 4 parameters: date, birth, 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 personal_month: 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.
personal_month 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 personal_month 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 personal_month. 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.
personal_month 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