AI agents call get_usage_analytics to retrieve information from Hi-AI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_usage_analytics only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
도구 사용 분석 및 통계를 조회합니다. 키워드: 분석, 통계, 사용량, analytics, statistics, usage 제공 정보: - 메모리 사용 통계 - 카테고리별 분포 - 시간별 사용 패턴 - 그래프 관계 통계 사용 예시: -. It is categorised as a Read tool in the Hi-AI MCP Server, which means it retrieves data without modifying state.
Register the Hi-AI MCP server in PolicyLayer and add a rule for get_usage_analytics: 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 Hi-AI. Nothing to install.
get_usage_analytics 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_usage_analytics 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_usage_analytics. 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_usage_analytics is provided by the Hi-AI MCP server (su-record/hi-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.