AI agents call get_post 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 analytics data (views, forwards, reactions, text) from a Telegram post. It performs a read-only query operation with no side effects, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an agent could retrieve post details it shouldn't have access to, but cannot alter or delete data.
From the tool's definition Tool name 'get_post' and description 'Get details of a single post: views, forwards, reactions, text' indicate retrieval of post metadata and content without modification or deletion.
Attacks that exploit this kind of access
Get details of a single post: views, forwards, reactions, text. 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_post: 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_post 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_post 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_post. 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_post 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 →