Give a custom name to your team collaboration session for easier identification.
AI agents use rename_team_collaboration to create or update resources in Automagik Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automagik Tools environment.
This tool modifies metadata (the name of a team collaboration session) in a reversible way. The operation updates an existing resource without deleting data or executing external code. The change can be undone by renaming again, making it a Write operation rather than Destructive. The blast radius is low—renaming a session only affects how it appears to users and does not impact data integrity or access controls.
From the tool's definition rename_team_collaboration: Give a custom name to your team collaboration session for easier identification.
Documented attack patterns abuse exactly the kind of access rename_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 rename_team_collaboration:
{
"version": "1",
"default": "deny",
"tools": {
"rename_team_collaboration": {
"limits": [
{
"counter": "rename_team_collaboration_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_team_collaboration 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.
Give a custom name to your team collaboration session for easier identification. It is categorised as a Write tool in the Automagik Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for rename_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.
rename_team_collaboration 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 rename_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 rename_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.
rename_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.