История Stars-транзакций (покупки/расходы).
AI agents call get_stars_transactions to retrieve information from Claudegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction history for Telegram Stars (a virtual currency in Telegram). It queries past financial data without creating, modifying, or deleting records, and does not move money or commit new financial obligations. While it relates to financial activity, it is strictly a read operation that returns historical information for review purposes.
From the tool's definition Tool name: 'get_stars_transactions'; description: 'История Stars-транзакций (покупки/расходы)' (History of Stars transactions (purchases/expenses)). The verb 'get' and 'история' (history) indicate data retrieval with no modification.
Attacks that exploit this kind of access
История Stars-транзакций (покупки/расходы). It is categorised as a Read tool in the Claudegram MCP Server, which means it retrieves data without modifying state.
Register the Claudegram MCP server in PolicyLayer and add a rule for get_stars_transactions: 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 Claudegram. Nothing to install.
get_stars_transactions 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_stars_transactions 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_stars_transactions. 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_stars_transactions is provided by the Claudegram MCP server (sanjar-x/claudegram). 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 →