AI agents invoke screen_share to trigger actions in Telegram MCP Complete. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Screen sharing initiates an active session that streams the user's screen to external parties. This is an Execute-level action as it triggers an external operation (broadcasting screen contents over Telegram calls) with significant privacy implications. Misuse could expose sensitive information visible on the screen to unintended recipients.
From the tool's definition 启用/停止屏幕共享 (Enable/Stop screen sharing)
Documented attack patterns abuse exactly the kind of access screen_share 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 screen_share:
{
"version": "1",
"default": "deny",
"tools": {
"screen_share": {
"limits": [
{
"counter": "screen_share_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}screen_share stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
启用/停止屏幕共享. It is categorised as a Execute tool in the Telegram MCP Complete MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for screen_share: 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.
screen_share is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the screen_share 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 screen_share. 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.
screen_share 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.