AI agents use addTimelineComment to create or update resources in Bitrix24 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitrix24 MCP Server environment.
This tool creates a new timeline comment, which modifies CRM data reversibly. The empty description reduces confidence slightly, but the naming convention and server context strongly suggest a Write operation. It is not Destructive (comments can be deleted), Execute (no code execution), or Financial.
From the tool's definition Tool name 'addTimelineComment' indicates creation of a new comment/note entry. The server description confirms CRUD operations on Bitrix24 CRM entities, and sibling tools like 'createActivity', 'createDeal', and 'createLead' establish the pattern that tools…
Documented attack patterns abuse exactly the kind of access addTimelineComment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitrix24 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for addTimelineComment:
{
"version": "1",
"default": "deny",
"tools": {
"addTimelineComment": {
"limits": [
{
"counter": "addtimelinecomment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addTimelineComment 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.
addTimelineComment. It is categorised as a Write tool in the Bitrix24 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitrix24 MCP Server MCP server in PolicyLayer and add a rule for addTimelineComment: 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 Bitrix24 MCP Server. Nothing to install.
addTimelineComment 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 addTimelineComment 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 addTimelineComment. 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.
addTimelineComment is provided by the Bitrix24 MCP Server MCP server (oneatdrt/bitrix24_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitrix24 MCP Server, 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.
25 Bitrix24 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.