Get health status for a specific tenant
AI agents call get_tenant_health to retrieve information from ACI 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 retrieval of health status information for a tenant. It has no side effects, does not modify configuration or data, and does not execute commands or trigger external operations. It is a straightforward query operation similar to 'get' or 'fetch' patterns. Low severity because health status retrieval poses minimal risk even if accessed by an AI agent with insufficient authorization.
From the tool's definition Tool name 'get_tenant_health' and description 'Get health status for a specific tenant' indicate a read-only query operation that retrieves monitoring/status data without modifying infrastructure.
Attacks that exploit this kind of access
Get health status for a specific tenant. It is categorised as a Read tool in the ACI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ACI MCP Server MCP server in PolicyLayer and add a rule for get_tenant_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 ACI MCP Server. Nothing to install.
get_tenant_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_tenant_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_tenant_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_tenant_health is provided by the ACI MCP Server MCP server (jim-coyne/aci_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 →