檢查藍圖小老鼠運行環境 檢測宿主環境（Antigravity/Cursor/VSCode）、API Key配置和依賴狀態。 Returns: JSON 格式的環境檢測報告
AI agents call check_bluemouse_environment to retrieve information from Bluemouse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/inspection tool that reads and reports on the state of the runtime environment (host system, API keys, dependencies). It performs no writes, deletions, code execution, or financial operations. The only potential risk is information disclosure of API keys in the report, but the tool's core function is read-only querying of environment status, making it a Read category tool with low severity.
From the tool's definition The tool 'check_bluemouse_environment' performs environment detection and returns a JSON report. Keywords: 'check', '檢查' (check), '檢測' (detect), reports on host environment, API Key configuration, and dependency status without modifying any state.
Documented attack patterns abuse exactly the kind of access check_bluemouse_environment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bluemouse, and nothing reaches the server without passing your rules. This is the rule we recommend for check_bluemouse_environment:
{
"version": "1",
"default": "deny",
"tools": {
"check_bluemouse_environment": {}
}
}check_bluemouse_environment 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.
檢查藍圖小老鼠運行環境 檢測宿主環境（Antigravity/Cursor/VSCode）、API Key配置和依賴狀態。 Returns: JSON 格式的環境檢測報告. It is categorised as a Read tool in the Bluemouse MCP Server, which means it retrieves data without modifying state.
Register the Bluemouse MCP server in PolicyLayer and add a rule for check_bluemouse_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 Bluemouse. Nothing to install.
check_bluemouse_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_bluemouse_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_bluemouse_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_bluemouse_environment is provided by the Bluemouse MCP server (peijun1700/bluemouse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Bluemouse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Bluemouse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.