AI agents invoke convert_to_apparent_solar_time to trigger actions in Ziwei Astrology MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a calculation/conversion operation using input parameters (time + coordinates) to produce a derived result. It doesn't purely retrieve stored data (Read), nor does it create or modify persistent data (Write). It's a computational transform, placing it in Execute. Severity is low as the blast radius of misuse is minimal — it only computes a time value with no external side effects.
From the tool's definition 将北京时间根据经纬度转换为真太阳时 — performs a time conversion computation (Beijing time to apparent solar time) based on geographic coordinates
Documented attack patterns abuse exactly the kind of access convert_to_apparent_solar_time gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ziwei Astrology MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_to_apparent_solar_time:
{
"version": "1",
"default": "deny",
"tools": {
"convert_to_apparent_solar_time": {
"limits": [
{
"counter": "convert_to_apparent_solar_time_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} convert_to_apparent_solar_time stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
将北京时间根据经纬度转换为真太阳时. It is categorised as a Execute tool in the Ziwei Astrology MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ziwei Astrology MCP Server MCP server in PolicyLayer and add a rule for convert_to_apparent_solar_time: 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 Ziwei Astrology MCP Server. Nothing to install.
convert_to_apparent_solar_time is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the convert_to_apparent_solar_time 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 convert_to_apparent_solar_time. 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.
convert_to_apparent_solar_time is provided by the Ziwei Astrology MCP Server MCP server (smogievogie/ziwei_iztro-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ziwei Astrology MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Ziwei Astrology MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.