level_health_check
Run a comprehensive health check on the level (overlaps, errors, warnings).
This record as markdown: /tools/quangdang46-uefn-verse-mcp/level-health-check.md
What level_health_check does on Uefn
AI agents call level_health_check to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why level_health_check is rated Low
This tool performs analysis and validation of the level without side effects. It queries the state of the level to identify issues and reports findings, consistent with Read category tools. Severity is low because misuse results in harmless information gathering.
From the tool's definition The description states 'Run a comprehensive health check on the level (overlaps, errors, warnings)' which indicates diagnostic/reporting functionality with no modification of state.
Attacks that exploit this kind of access
The rule that runs level_health_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For level_health_check, this is the rule to start with:
level_health_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every level_health_check call is checked against it from then on.
Questions about level_health_check
Run a comprehensive health check on the level (overlaps, errors, warnings). It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for level_health_check: 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 Uefn. Nothing to install.
level_health_check 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 level_health_check 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 level_health_check. 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.
level_health_check is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue