This record as markdown: /tools/funny-booth-aos-mcp-server/get-members.md
What get_members does on Aos
AI agents call get_members to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
Parameters from the server's own tool schema.
Why get_members is rated Low
The tool retrieves member data with no described side effects. Although the description is empty, the 'get_' prefix is a strong signal of a read-only query. The blast radius of exposing member list retrieval is low, assuming it respects access controls. Confidence is slightly reduced due to missing description, but the semantic clarity of the name is sufficient.
From the tool's definition Tool name 'get_members' is a retrieval operation; the naming pattern ('get_*') combined with sibling tools that clearly perform writes (create_task, create_issue, create_member, etc.) indicates this fetches data without modification.
Attacks that exploit this kind of access
The rule that runs get_members 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 get_members, this is the rule to start with:
get_members is read-only, so it stays allowed. 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 get_members call is checked against it from then on.
Questions about get_members
get_members is a read tool on the Aos MCP server. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
get_members accepts 1 parameter: team_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 get_members: 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.
get_members is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_members 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 get_members. 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.
get_members 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