Check the server environment
AI agents call check_environment to retrieve information from Google Tag Manager 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 environmental configuration or status details without modifying, executing operations, or deleting resources. It is a diagnostic/informational read operation typical of system health checks or configuration inspection. The minimal blast radius and read-only nature justify low severity.
From the tool's definition Tool name 'check_environment' and description 'Check the server environment' indicate querying/retrieving environment status information with no side effects.
Attacks that exploit this kind of access
Check the server environment. It is categorised as a Read tool in the Google Tag Manager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for check_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 Google Tag Manager MCP Server. Nothing to install.
check_environment 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 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. 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 is provided by the Google Tag Manager MCP Server MCP server (neep305/mcp-for-gtm). 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 →