Transfer coordinator role to another member. Only current coordinator can initiate. Target must be existing member.
AI agents use handover_coordinator to create or update resources in Brainstorm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brainstorm environment.
This tool modifies the coordination/role state of a project by reassigning the coordinator role from one member to another. It is a reversible role change (the coordinator role could be transferred back), placing it in the Write category. The blast radius is medium because misuse could disrupt project coordination by transferring control to an unintended member, but it does not delete data or execute arbitrary code.
From the tool's definition Transfer coordinator role to another member. Only current coordinator can initiate. Target must be existing member.
Documented attack patterns abuse exactly the kind of access handover_coordinator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Brainstorm, and nothing reaches the server without passing your rules. This is the rule we recommend for handover_coordinator:
{
"version": "1",
"default": "deny",
"tools": {
"handover_coordinator": {
"limits": [
{
"counter": "handover_coordinator_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}handover_coordinator 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.
Transfer coordinator role to another member. Only current coordinator can initiate. Target must be existing member. It is categorised as a Write tool in the Brainstorm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Brainstorm MCP server in PolicyLayer and add a rule for handover_coordinator: 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 Brainstorm. Nothing to install.
handover_coordinator 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 handover_coordinator 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 handover_coordinator. 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.
handover_coordinator is provided by the Brainstorm MCP server (theodorstorm/brainstorm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Brainstorm, 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.
17 Brainstorm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.