This record as markdown: /tools/funny-booth-aos-mcp-server/create-team.md
What create_team does on Aos
AI agents use create_team to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | チーム名 |
Parameters from the server's own tool schema.
Why create_team is rated Medium
The name 'create_team' suggests reversible creation of a team object (organizational/administrative resource), a Write category action. Severity is low because team creation typically has limited blast radius—teams can be deleted or recreated. Confidence is moderate (0.6) because the tool description is empty, limiting assessment of side effects, scope, or constraints.
From the tool's definition Tool name is 'create_team' indicating a creation operation without explicit delete/modify/execute/financial semantics in the name.
Attacks that exploit this kind of access
The rule that runs create_team safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_team, this is the rule to start with:
create_team 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every create_team call is checked against it from then on.
Questions about create_team
create_team is a write tool on the Aos MCP server. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_team accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Aos 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 Aos. 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 Aos MCP server (@funny-booth/aos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue