list_user_teams
List all teams you belong to. Use this to discover available teams before filtering knowledge base operations by team. Returns team ID, name, your role, and member count.
This record as markdown: /tools/flowdot-llc-mcp-server/list-user-teams.md
What list_user_teams does on FlowDot MCP Server
AI agents call list_user_teams to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_user_teams is rated Low
This tool performs a straightforward data retrieval operation that queries team membership information. It has no side effects, does not modify any data, and does not trigger external operations. The severity is low because the information returned is scoped to the user's own team memberships and carries minimal risk if exposed to agent misuse.
From the tool's definition 'List all teams you belong to' - retrieves existing team data with no modification capability. Returns read-only information: 'team ID, name, your role, and member count'.
Attacks that exploit this kind of access
The rule that runs list_user_teams safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_user_teams, this is the rule to start with:
list_user_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 FlowDot MCP Server, apply this rule, and every list_user_teams call is checked against it from then on.
Questions about list_user_teams
List all teams you belong to. Use this to discover available teams before filtering knowledge base operations by team. Returns team ID, name, your role, and member count. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for list_user_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 FlowDot MCP Server. Nothing to install.
list_user_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_user_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_user_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_user_teams is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue