AI agents use edit_message to create or update resources in Tgmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tgmcp environment.
This tool creates or modifies data reversibly by allowing a user to edit previously sent messages. While it changes content, the operation is reversible (messages can be edited again) and does not irreversibly delete data. It falls squarely into the Write category.
From the tool's definition Tool name 'edit_message' and description 'Edit a message you sent' indicate modification of existing content.
Attacks that exploit this kind of access
Edit a message you sent. It is categorised as a Write tool in the Tgmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tg MCP server in PolicyLayer and add a rule for edit_message: 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 Tgmcp. Nothing to install.
edit_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edit_message 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 edit_message. 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.
edit_message is provided by the Tg MCP server (oevortex/tgmcp). 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 →