bitrix_comment · Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What bitrix_comment does on Email MCP Server

AI agents use bitrix_comment to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.

WHY IT NEEDS A POLICY

Why bitrix_comment needs a policy

The bitrix_comment tool performs multiple operations: adding comments (Write), updating comments (Write), listing comments (Read), and deleting comments (Destructive). Since the tool encompasses both reversible modifications and irreversible deletions, the most severe category applies. However, the framing suggests comment management rather than focused deletion.

From the tool's definition Tool supports add, update, and delete operations on comments. While add and update are reversible Write operations ("Add comment", "Update comment"), the delete action is irreversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitrix_comment Rate-limited

bitrix_comment 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitrix_comment": {
      "limits": [
        {
          "counter": "bitrix_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Email MCP Server, so you can run agents against it safely.

FAQ

Questions about bitrix_comment

What does the bitrix_comment tool do? +

Task comment management. Actions: - add: Add comment (requires taskId, text) - list: List comments (requires taskId) - update: Update comment (requires taskId, commentId, text) - delete: Delete comment (requires taskId, commentId). It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bitrix_comment? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_comment: 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 Email MCP Server. Nothing to install.

What risk level is bitrix_comment? +

bitrix_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bitrix_comment? +

Yes. Add a rate_limit block to the bitrix_comment 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.

How do I block bitrix_comment completely? +

Set action: deny in the PolicyLayer policy for bitrix_comment. 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.

What MCP server provides bitrix_comment? +

bitrix_comment is provided by the Email MCP Server MCP server (sventern/mcp_email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.