team_list

Lists AI teams owned by the authenticated tenant. Requires team:read. Returns no other tenant data.

SERVERHamza Agent Hub 252 SOURCEhamzachallenge3-dev/hamza-agent-hub-252

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/hamza-agent-hub-252/team-list.md

WHAT IT DOES

What team_list does on Hamza Agent Hub 252

AI agents call team_list to retrieve information from Hamza Agent Hub 252 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_list is rated Low

Retrieves team metadata scoped to authenticated tenant; no side effects or data modification.

From the tool's definition Lists AI teams owned by authenticated tenant. Requires team:read.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs team_list safely

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

team_list Allowed

team_list 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_list": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every team_list call is checked against it from then on.

FAQ

Questions about team_list

What does the team_list tool do? +

Lists AI teams owned by the authenticated tenant. Requires team:read. Returns no other tenant data. It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on team_list? +

Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for team_list: 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 Hamza Agent Hub 252. Nothing to install.

What risk level is team_list? +

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

Can I rate-limit team_list? +

Yes. Add a rate_limit block to the team_list 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_list completely? +

Set action: deny in the PolicyLayer policy for team_list. 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_list? +

team_list is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hamza Agent Hub 252, and thousands of servers like it.

This server

All 581 Hamza Agent Hub 252 tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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