team_get

Reads one AI team owned by the authenticated tenant. Requires team:read. Foreign and missing IDs both return not_found.

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/team-get.md

WHAT IT DOES

What team_get does on Claude Flow

AI agents call team_get to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why team_get is rated Low

Simple read-only retrieval of team data with no side effects or modifications.

From the tool's definition Reads one AI team owned by the authenticated tenant.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs team_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For team_get, this is the rule to start with:

team_get Allowed

team_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "team_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every team_get call is checked against it from then on.

FAQ

Questions about team_get

What does the team_get tool do? +

Reads one AI team owned by the authenticated tenant. Requires team:read. Foreign and missing IDs both return not_found. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on team_get? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for team_get: 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 Claude Flow. Nothing to install.

What risk level is team_get? +

team_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit team_get? +

Yes. Add a rate_limit block to the team_get 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.

How do I block team_get completely? +

Set action: deny in the PolicyLayer policy for team_get. 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.

What MCP server provides team_get? +

team_get is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 546 Claude Flow tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →