AI agents use send_contact to create or update resources in Telegram MCP Complete — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Complete environment.
Sending a contact card creates new message data in Telegram chats but does not irreversibly delete data, execute arbitrary code, or move funds. It is reversible (messages can be deleted). Given the multi-account capability of this server and potential for contact spam or unauthorized contact sharing across accounts, the severity is medium rather than low.
From the tool's definition Tool name 'send_contact' and description '发送联系人卡片' (send contact card) indicate the tool sends/transmits contact information through Telegram. This is a write operation that creates/transmits a new message object containing contact data.
Documented attack patterns abuse exactly the kind of access send_contact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for send_contact:
{
"version": "1",
"default": "deny",
"tools": {
"send_contact": {
"limits": [
{
"counter": "send_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_contact stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
发送联系人卡片. It is categorised as a Write tool in the Telegram MCP Complete MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for send_contact: 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 Telegram MCP Complete. Nothing to install.
send_contact 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 send_contact 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 send_contact. 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.
send_contact is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Complete, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
153 Telegram MCP Complete tools catalogued and risk-classified — across an index of 43,000+ MCP servers.