检查Wiki API服务健康状态
AI agents call check_wiki_api_health to retrieve information from Minecraft Wiki MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a health check on the Wiki API, which is a non-invasive diagnostic operation that retrieves status information without side effects. It is purely informational and does not create, modify, delete, or execute any operations. This is a classic Read category tool with minimal risk (low severity) and very high confidence.
From the tool's definition Tool name 'check_wiki_api_health' and description '检查Wiki API服务健康状态' (Check Wiki API service health status) indicate a read-only query of service status. No data retrieval, modification, code execution, or destructive operations are involved.
Attacks that exploit this kind of access
检查Wiki API服务健康状态. It is categorised as a Read tool in the Minecraft Wiki MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Minecraft Wiki MCP Server MCP server in PolicyLayer and add a rule for check_wiki_api_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 Minecraft Wiki MCP Server. Nothing to install.
check_wiki_api_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_wiki_api_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_wiki_api_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_wiki_api_health is provided by the Minecraft Wiki MCP Server MCP server (rice-awa/mc-wiki-mcp-pypi). 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 →