This record as markdown: /tools/funny-booth-aos-mcp-server/create-member.md
What create_member does on Aos
AI agents use create_member 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 | — | 役割（既定 staff） |
email | string | — | メールアドレス |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
Parameters from the server's own tool schema.
Why create_member is rated Medium
The tool name 'create_member' and context (AOS project management server with multiple create operations) indicate it creates a new member entity, which is reversible data creation. No destructive deletion, financial impact, or code execution is implied. Severity is medium because creating unauthorized team members could impact team roster and access control, though the effect is reversible.
From the tool's definition Tool name 'create_member' indicates creation of a new entity. Sibling tools include 'create_task', 'create_todo', 'create_issue', 'create_kpi_metric', 'create_mission', 'create_team' — all Write operations. Pattern suggests this tool creates a member resource.
Attacks that exploit this kind of access
The rule that runs create_member 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_member, this is the rule to start with:
create_member 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_member call is checked against it from then on.
Questions about create_member
create_member 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_member 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 create_member: 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_member 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_member 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_member. 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_member 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