Список установленных стикерсетов.
AI agents call get_installed_stickers 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 a list of sticker sets installed on the user's Telegram account. It performs a read-only query with no side effects—it does not create, modify, delete data, execute code, or trigger financial transactions. The blast radius of misuse is minimal; an attacker could only learn which stickers the user has installed, which is informational only.
From the tool's definition Tool name 'get_installed_stickers' and description 'Список установленных стикерсетов' (List of installed sticker sets) indicate a retrieval operation that queries user data without modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Список установленных стикерсетов. 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_installed_stickers: 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_installed_stickers 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_installed_stickers 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_installed_stickers. 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_installed_stickers 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 →