Start a collaborative session with a team of agents. Describe your task and the team will work together.
AI agents invoke start_team_collaboration to trigger actions in Automagik Tools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers execution of external agent operations (team collaboration workflows) based on user input. While the effects are somewhat bounded by the collaborative agent framework, the actual operations performed depend entirely on the task description provided, making it an Execute category tool.
From the tool's definition Tool description states 'Start a collaborative session with a team of agents' and 'the team will work together' on a user-described task. This initiates execution of agent workflows whose effects depend on the task description provided as an argument.
Documented attack patterns abuse exactly the kind of access start_team_collaboration gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for start_team_collaboration:
{
"version": "1",
"default": "deny",
"tools": {
"start_team_collaboration": {
"limits": [
{
"counter": "start_team_collaboration_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_team_collaboration stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start a collaborative session with a team of agents. Describe your task and the team will work together. It is categorised as a Execute tool in the Automagik Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for start_team_collaboration: 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 Automagik Tools. Nothing to install.
start_team_collaboration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_team_collaboration 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 start_team_collaboration. 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.
start_team_collaboration is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.