get_health
Get API health status and uptime information
This record as markdown: /tools/instantkom-mcp-server/get-health.md
What get_health does on instantKOM MCP Server
AI agents call get_health to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_health is rated Low
This is a diagnostic/monitoring tool that queries system health metrics. It has no side effects, makes no modifications, executes no code, and returns only informational status data. This is a classic Read operation with minimal blast radius even if accessed by an AI agent.
From the tool's definition Tool name 'get_health' and description 'Get API health status and uptime information' indicate a read-only query that retrieves status data without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_health, this is the rule to start with:
get_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every get_health call is checked against it from then on.
Questions about get_health
Get API health status and uptime information. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for get_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 instantKOM MCP Server. Nothing to install.
get_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_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_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_health is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue