AI agents call getSolarTimes to retrieve information from Bazi MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns calendar/time data. It has no side effects, does not modify any data, does not execute code or shell commands, and does not involve financial transactions. The operation is informational only, returning formatted time values based on input Bazi calculations.
From the tool's definition The tool 'getSolarTimes' retrieves a list of solar calendar times (公历时间列表) based on Bazi data. The description indicates it returns time information in a standard format (YYYY-MM-DD hh:mm:ss), which is a data retrieval operation with no modification,…
Attacks that exploit this kind of access
根据八字获取公历时间列表。返回的时间格式为：YYYY-MM-DD hh:mm:ss。例如时间1998年7月31日下午2点整表示为：1998-07-31 14:00:00. It is categorised as a Read tool in the Bazi MCP MCP Server, which means it retrieves data without modifying state.
Register the Bazi MCP server in PolicyLayer and add a rule for getSolarTimes: 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 Bazi MCP. Nothing to install.
getSolarTimes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getSolarTimes 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 getSolarTimes. 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.
getSolarTimes is provided by the Bazi MCP server (shuangzixing1976/bazi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →