Low Risk

get_environment

Retrieves a single Lenses environment by name.

How to control get_environment ↓

What get_environment does on Lenses MCP Server

AI agents call get_environment 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.

Low Risk

Why get_environment needs a policy

This tool retrieves configuration or metadata about a Lenses environment without modifying, deleting, or executing any operations. It is a simple read operation that queries existing data. The low severity reflects that unauthorized retrieval of environment metadata poses minimal risk compared to tools that modify infrastructure or delete data (which are present as siblings on this server).

From the tool's definition Tool name 'get_environment' and description 'Retrieves a single Lenses environment by name' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_environment gives an agent:

How to control get_environment

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 get_environment:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_environment": {}
  }
}

get_environment is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Lenses MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_environment

What does the get_environment tool do? +

Retrieves a single Lenses environment by name. It is categorised as a Read tool in the Lenses MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_environment? +

Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for get_environment: 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.

What risk level is get_environment? +

get_environment is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_environment? +

Yes. Add a rate_limit block to the get_environment 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.

How do I block get_environment completely? +

Set action: deny in the PolicyLayer policy for get_environment. 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.

What MCP server provides get_environment? +

get_environment 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.

Enforce policy on every Lenses MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.