AI agents call check_health to retrieve information from Moomoo Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a health/connectivity check, which is a non-destructive query operation that returns status information. It has no side effects, does not execute trades, does not modify data, and does not involve financial transactions. It falls squarely within the Read category as a diagnostic retrieval operation.
From the tool's definition Tool name is 'check_health' and description states it 'Check[s] connectivity to Moomoo and MCP server health.' This is a diagnostic query that retrieves status information without modifying, executing, or committing any financial transactions.
Documented attack patterns abuse exactly the kind of access check_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Moomoo Api, and nothing reaches the server without passing your rules. This is the rule we recommend for check_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_health": {}
}
}check_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check connectivity to Moomoo and MCP server health. It is categorised as a Read tool in the Moomoo Api MCP Server, which means it retrieves data without modifying state.
Register the Moomoo Api MCP server in PolicyLayer and add a rule for check_health: 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 Moomoo Api. Nothing to install.
check_health 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 check_health 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 check_health. 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.
check_health is provided by the Moomoo Api MCP server (litash/moomoo-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Moomoo Api, 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.
22 Moomoo Api tools catalogued and risk-classified — across an index of 43,000+ MCP servers.