Zip a project directory and send it to the user
AI agents use zip_project to create or update resources in MCP-Communicator-Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Communicator-Telegram environment.
The tool creates a compressed archive (Write operation: creates new data artifact) and sends it via Telegram. While the underlying project files are not modified, the zip operation itself generates new data and the transmission is a write/send action. This is reversible (the zip can be deleted), so it does not qualify as Destructive.
From the tool's definition Tool description states: 'Zip a project directory and send it to the user' — involves creating a new archive file (zip) and transmitting it, which are reversible write operations.
Documented attack patterns abuse exactly the kind of access zip_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Communicator-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for zip_project:
{
"version": "1",
"default": "deny",
"tools": {
"zip_project": {
"limits": [
{
"counter": "zip_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zip_project 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.
Zip a project directory and send it to the user. It is categorised as a Write tool in the MCP-Communicator-Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Communicator-Telegram MCP server in PolicyLayer and add a rule for zip_project: 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 MCP-Communicator-Telegram. Nothing to install.
zip_project 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 zip_project 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 zip_project. 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.
zip_project is provided by the MCP-Communicator-Telegram MCP server (qpd-v/mcp-communicator-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 MCP-Communicator-Telegram tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 MCP-Communicator-Telegram tools catalogued and risk-classified — across an index of 42,500+ MCP servers.