获取当前 MCP 服务端的全部环境配置信息（GitLab、Jenkins、PIPE_TEMPLATE 等）。AI 可通过此工具一次性获取所有连接配置，无需逐个猜测环境变量。敏感 token 会做脱敏处理，仅展示前4位。
AI agents call get_env_config to retrieve information from Postar Pipe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a Read operation—it queries and retrieves configuration data with no side effects. However, severity is high rather than low because: (1) it exposes system credentials and authentication tokens (even if partially masked), (2) the first 4 characters of tokens can aid in enumeration attacks or credential guessing, (3) full environment configuration exposure could reveal internal infrastructure…
From the tool's definition The tool name is 'get_env_config' and description states it '获取当前 MCP 服务端的全部环境配置信息' (retrieves all environment configuration information of the current MCP server).
Attacks that exploit this kind of access
获取当前 MCP 服务端的全部环境配置信息（GitLab、Jenkins、PIPE_TEMPLATE 等）。AI 可通过此工具一次性获取所有连接配置，无需逐个猜测环境变量。敏感 token 会做脱敏处理，仅展示前4位。. It is categorised as a Read tool in the Postar Pipe MCP Server, which means it retrieves data without modifying state.
Register the Postar Pipe MCP server in PolicyLayer and add a rule for get_env_config: 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 Postar Pipe. Nothing to install.
get_env_config 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 get_env_config 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 get_env_config. 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.
get_env_config is provided by the Postar Pipe MCP server (postar-pipe-mcp). 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 →