Purpose: Check that the RawTree API endpoint is reachable. NOT for: Validating database permissions or checking whether a specific table exists. Use list-tables or run-query for authenticated checks. Returns: The RawTree health response. When to use: - User asks whether RawTree is up - You are de...
AI agents call check-health to retrieve information from RawTree MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the availability/status of a remote service with no side effects, no data access, and no capability to modify, execute against, or delete resources. It is a pure diagnostic read operation with minimal blast radius if misused by an agent—worst case, redundant health checks waste API calls.
From the tool's definition check-health returns a health response and is explicitly described as checking API endpoint reachability without performing data access, validation, or modification.
Attacks that exploit this kind of access
Purpose: Check that the RawTree API endpoint is reachable. NOT for: Validating database permissions or checking whether a specific table exists. Use list-tables or run-query for authenticated checks. Returns: The RawTree health response. When to use: - User asks whether RawTree is up - You are debugging MCP configuration before using authenticated tools. It is categorised as a Read tool in the RawTree MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RawTree MCP Server MCP server in PolicyLayer and add a rule for check-health: 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 RawTree MCP Server. Nothing to install.
check-health 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-health 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-health. 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-health is provided by the RawTree MCP Server MCP server (rawtreedb/rawtree-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 →