AI agents call list_environments 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 retrieves and enumerates environment configurations without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk unless the environment list itself contains highly sensitive information, but listing environments in a management system is typically low-risk metadata retrieval.
From the tool's definition Tool name 'list_environments' and description 'Lists all Lenses environments' indicate a query/retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access list_environments 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 list_environments:
{
"version": "1",
"default": "deny",
"tools": {
"list_environments": {}
}
}list_environments 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.
Lists all Lenses environments. 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 list_environments: 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.
list_environments 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 list_environments 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 list_environments. 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.
list_environments 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.