This record as markdown: /tools/funny-booth-aos-mcp-server/list-teams.md
What list_teams does on Aos
AI agents call list_teams 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.
Why list_teams is rated Low
The 'list_' prefix is a standard pattern for read operations that query and return data without modification. Given the lack of description and a pattern of other Create/Complete tools on the server, this tool follows the Read category paradigm: it retrieves or lists existing teams. No write, execute, destructive, or financial operations are evident from the name or context.
From the tool's definition Tool name 'list_teams' indicates a query/list operation that retrieves team data with no side effects. Sibling tools include create_* and complete_* verbs that modify state, but list_teams performs only retrieval.
Attacks that exploit this kind of access
The rule that runs list_teams 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 list_teams, this is the rule to start with:
list_teams 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 list_teams call is checked against it from then on.
Questions about list_teams
list_teams 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.
Register the Aos MCP server in PolicyLayer and add a rule for list_teams: 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.
list_teams 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 list_teams 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 list_teams. 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.
list_teams 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