AI agents call get_usage to retrieve information from Tgstat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account usage and quota statistics, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—exposing usage data is generally non-harmful. Classified as Read with low severity.
From the tool's definition Tool description states 'Show your TGStat API usage and quota' — a retrieval operation that queries account/quota information without modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Show your TGStat API usage and quota: requests / channels / words spent vs allowed, and package expiry. It is categorised as a Read tool in the Tgstat MCP Server, which means it retrieves data without modifying state.
Register the Tgstat MCP server in PolicyLayer and add a rule for get_usage: 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 Tgstat. Nothing to install.
get_usage 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 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. 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 is provided by the Tgstat MCP server (theyahia/tgstat-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 →