bitrix_task_approve · Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What bitrix_task_approve does on Email MCP Server

AI agents use bitrix_task_approve 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_task_approve needs a policy

The tool changes task approval status from pending to accepted, which is a data modification operation. This is reversible (approval can be revoked or reset), so it falls under Write rather than Destructive. Severity is medium because misuse could approve unauthorized work, potentially leading to payment issuance or workflow confusion, but the impact is containable within a task management system.

From the tool's definition Tool description states 'Approve a completed task in Bitrix24 (accept the work)' — this modifies task state by changing approval status, a reversible state change on task records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitrix_task_approve Rate-limited

bitrix_task_approve 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_task_approve": {
      "limits": [
        {
          "counter": "bitrix_task_approve_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_task_approve

What does the bitrix_task_approve tool do? +

Approve a completed task in Bitrix24 (accept the work). 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_task_approve? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_task_approve: 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_task_approve? +

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

Can I rate-limit bitrix_task_approve? +

Yes. Add a rate_limit block to the bitrix_task_approve 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_task_approve completely? +

Set action: deny in the PolicyLayer policy for bitrix_task_approve. 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_task_approve? +

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