AI agents use add_activity to create or update resources in MCP-BPMN Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-BPMN Server environment.
This tool creates new BPMN diagram elements (activities/tasks) which are reversible modifications to the diagram structure. It does not execute external code, delete data irreversibly, or move money. The severity is medium because misuse could bloat or corrupt a diagram, but changes can be undone through the Write operations available on this server (implied by the presence of other add/manipulate tools).
From the tool's definition Tool name is 'add_activity' and description states 'Add an activity to the current diagram'. The verb 'add' indicates creation of new diagram elements.
Documented attack patterns abuse exactly the kind of access add_activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-BPMN Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_activity:
{
"version": "1",
"default": "deny",
"tools": {
"add_activity": {
"limits": [
{
"counter": "add_activity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_activity 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.
Add an activity to the current diagram. It is categorised as a Write tool in the MCP-BPMN Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-BPMN Server MCP server in PolicyLayer and add a rule for add_activity: 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-BPMN Server. Nothing to install.
add_activity 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 add_activity 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 add_activity. 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.
add_activity is provided by the MCP-BPMN Server MCP server (oisee/mcp-bpmn). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-BPMN 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.
41 MCP-BPMN Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.