Checks the health status of a Lenses environment.
AI agents call check_environment_health to retrieve information from Lenses 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 read-only health check operation. It queries the status of an environment and returns information without side effects, making it a Read category tool. The severity is low because health status checks have minimal blast radius—they cannot modify data, execute commands, or cause financial impact. Even if misused by an AI agent, the only consequence would be reading environment metadata.
From the tool's definition Tool description states it 'Checks the health status of a Lenses environment' — a query operation that retrieves status information without modifying or executing actions on the underlying data or systems.
Documented attack patterns abuse exactly the kind of access check_environment_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lenses MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_environment_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_environment_health": {}
}
}check_environment_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.
Checks the health status of a Lenses environment. It is categorised as a Read tool in the Lenses MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for check_environment_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 Lenses MCP Server. Nothing to install.
check_environment_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_environment_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_environment_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_environment_health is provided by the Lenses MCP Server MCP server (lensesio/lenses-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lenses 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.
42 Lenses MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.