save_draft
AI agents use save_draft to create or update resources in Claudegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudegram environment.
Saving a draft creates or updates a reversible message artifact in the user's Telegram account. This is a Write operation—it modifies data without permanent deletion or code execution. Severity is medium because misuse could create misleading drafts or spam-like message artifacts in the user's account, but the effects are easily reversible via clear_draft or manual deletion.
From the tool's definition Tool name 'save_draft' indicates it modifies draft message state in Telegram. The description is empty, but context from server description ('messaging, media, chat management') and sibling tools (clear_draft, which explicitly manages drafts) confirms this…
Attacks that exploit this kind of access
save_draft. It is categorised as a Write tool in the Claudegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claudegram MCP server in PolicyLayer and add a rule for save_draft: 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.
save_draft 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 save_draft 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 save_draft. 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.
save_draft 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 →