List existing Telegram ad campaigns in Click.ru account.
AI agents call get_telegram_ads to retrieve information from SergeyKrin9/mcp Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about existing Telegram ad campaigns without modifying, deleting, or executing any operations. It is a straightforward data retrieval operation, making it a Read category risk with low severity since misuse would only expose information about existing campaigns rather than cause financial loss, data destruction, or unauthorized actions.
From the tool's definition Tool name is 'get_telegram_ads' and description states 'List existing Telegram ad campaigns in Click.ru account.' The verb 'List' and action of retrieving/querying existing data indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
List existing Telegram ad campaigns in Click.ru account. It is categorised as a Read tool in the SergeyKrin9/mcp Servers MCP Server, which means it retrieves data without modifying state.
Register the SergeyKrin9/mcp Servers MCP server in PolicyLayer and add a rule for get_telegram_ads: 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 SergeyKrin9/mcp Servers. Nothing to install.
get_telegram_ads 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_telegram_ads 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_telegram_ads. 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_telegram_ads is provided by the SergeyKrin9/mcp Servers MCP server (sergeykrin9/mcp-servers). 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 →