Check the health status of the Plantos API and database connection.
AI agents call get_api_health to retrieve information from Plantos 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 health check of API and database infrastructure. It queries and returns status information with no side effects, data modifications, or external operations. It falls squarely into the Read category with low severity due to minimal blast radius if misused—at worst, an agent could repeatedly check health status without causing harm.
From the tool's definition Tool name 'get_api_health' and description 'Check the health status of the Plantos API and database connection' indicates a diagnostic query operation that retrieves status information without modifying any data.
Attacks that exploit this kind of access
Check the health status of the Plantos API and database connection. It is categorised as a Read tool in the Plantos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Plantos MCP Server MCP server in PolicyLayer and add a rule for get_api_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 Plantos MCP Server. Nothing to install.
get_api_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 get_api_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 get_api_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.
get_api_health is provided by the Plantos MCP Server MCP server (plantos-sensor/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 →