bitrix_task_favorite_remove · Email MCP Server MCP

WHAT IT DOES

What bitrix_task_favorite_remove does on Email MCP Server

AI agents use bitrix_task_favorite_remove 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_favorite_remove needs a policy

Removing a task from favorites is a reversible modification to user preferences/settings — the task itself is not deleted, only its 'favorite' status is toggled. This is a Write operation (modifies user data) rather than Destructive, since the task remains intact and the action can be undone by re-adding it to favorites. Blast radius is low as it only affects a personal favorites list.

From the tool's definition Remove a task from favorites in Bitrix24

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitrix_task_favorite_remove Rate-limited

bitrix_task_favorite_remove 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_favorite_remove": {
      "limits": [
        {
          "counter": "bitrix_task_favorite_remove_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_favorite_remove

What does the bitrix_task_favorite_remove tool do? +

Remove a task from favorites in Bitrix24. 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_favorite_remove? +

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

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

Can I rate-limit bitrix_task_favorite_remove? +

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

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

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

// THE FULL RECORD

bitrix_task_favorite_remove is one line of Email MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →