Check the availability of the current device API interface (Connection Status)
AI agents call check-status to retrieve information from TgeBrowser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to verify connectivity and availability of the API interface. It has no side effects, cannot modify data, and poses minimal risk if invoked by an AI agent. The worst-case scenario is receiving accurate or inaccurate status information, which does not enable further harmful actions on its own.
From the tool's definition Tool name 'check-status' and description 'Check the availability of the current device API interface (Connection Status)' indicate a query operation that retrieves status information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check the availability of the current device API interface (Connection Status). It is categorised as a Read tool in the TgeBrowser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TgeBrowser MCP Server MCP server in PolicyLayer and add a rule for check-status: 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 TgeBrowser MCP Server. Nothing to install.
check-status 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-status 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-status. 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-status is provided by the TgeBrowser MCP Server MCP server (tuguang2025/tgebrowser-mcp-server). 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 →