This record as markdown: /tools/funny-booth-aos-mcp-server/update-seat.md
What update_seat does on Aos
AI agents use update_seat 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 |
|---|---|---|---|
seat | string | Yes | 座席名 |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
member_id | string | null | — | 割当メンバーID（null で空席化） |
responsibilities | array | — | 責務リスト |
Parameters from the server's own tool schema.
Why update_seat is rated Medium
Update operations are reversible modifications (Write category). Severity is medium because updating seat assignments could affect multiple users' access or permissions, but lack of destructive capability and financial impact limits it from higher severity. Confidence is reduced from high due to empty description—cannot confirm exact nature of what 'seat' encompasses or scope of changes possible.
From the tool's definition Tool name is 'update_seat' with empty description. The verb 'update' indicates modification of data. Context of sibling tools (create_task, create_issue, create_member, create_team) suggests a task/project management system where 'seat' likely refers to user…
Attacks that exploit this kind of access
The rule that runs update_seat 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 update_seat, this is the rule to start with:
update_seat 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 update_seat call is checked against it from then on.
Questions about update_seat
update_seat 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.
update_seat accepts 4 parameters: seat, team_id, member_id, responsibilities. Required: seat. 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 update_seat: 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.
update_seat 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 update_seat 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 update_seat. 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.
update_seat 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