This record as markdown: /tools/funny-booth-aos-mcp-server/update-member.md
What update_member does on Aos
AI agents use update_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 |
|---|---|---|---|
id | string | Yes | メンバーID |
name | string | — | |
role | string | — | |
email | string | null | — | null でクリア |
Parameters from the server's own tool schema.
Why update_member is rated Medium
The 'update_member' tool modifies existing member records. This is classified as Write because updates are typically reversible (members can be updated again or reverted). Severity is medium due to potential impact on user/team data—an AI agent could maliciously alter member attributes (roles, permissions, contact info)—but the operation is not destructive or financial.
From the tool's definition Tool name 'update_member' indicates modification of member data. Description is empty, preventing precise scope assessment. Sibling tools include create_member, suggesting a member management system where updates are reversible changes.
Attacks that exploit this kind of access
The rule that runs update_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 update_member, this is the rule to start with:
update_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 update_member call is checked against it from then on.
Questions about update_member
update_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.
update_member accepts 4 parameters: id, name, role, email. Required: id. 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_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.
update_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 update_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 update_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.
update_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