This record as markdown: /tools/funny-booth-aos-mcp-server/invite-to-team.md
What invite_to_team does on Aos
AI agents use invite_to_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 | 招待するメンバー名 |
role | string | — | |
email | string | — | メールアドレス |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
Parameters from the server's own tool schema.
Why invite_to_team is rated Medium
Inviting a user to a team creates a new membership relationship and modifies team composition—a reversible write operation. This is less severe than execute (no code/arbitrary operations) or destructive (reversible). Severity is medium because a compromised agent could add unauthorized members to sensitive teams, but the action is reversible.
From the tool's definition Tool named 'invite_to_team' with empty description; sibling tools on server include 'create_member', 'create_team', 'create_task', indicating a team/project management system. The name 'invite_to_team' suggests adding users to a group.
Attacks that exploit this kind of access
The rule that runs invite_to_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 invite_to_team, this is the rule to start with:
invite_to_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 invite_to_team call is checked against it from then on.
Questions about invite_to_team
invite_to_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.
invite_to_team accepts 4 parameters: name, role, email, team_id. 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 invite_to_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.
invite_to_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 invite_to_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 invite_to_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.
invite_to_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