Create a new team for knowledge sharing.
AI agents use create_team to create or update resources in Session Buddy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Session Buddy environment.
This tool creates new organizational/collaborative entities (teams) for knowledge sharing. It is a Write operation because it creates new data structures reversibly—teams can be modified or deleted. The blast radius is low: creating an unwanted team is inconvenient but not destructive, does not execute arbitrary code, and involves no financial impact.
From the tool's definition Tool is named 'create_team' and described as creating 'a new team for knowledge sharing,' which is a data creation operation with no irreversible consequences.
Attacks that exploit this kind of access
Create a new team for knowledge sharing. It is categorised as a Write tool in the Session Buddy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Session Buddy MCP server in PolicyLayer and add a rule for create_team: 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 Session Buddy. Nothing to install.
create_team 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 create_team 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 create_team. 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.
create_team is provided by the Session Buddy MCP server (lesleslie/session-buddy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →