team_templates_list
Lists first-party AI-team playbooks and their roles. Requires team:read. Does not create or run a team.
This record as markdown: /tools/hamza-agent-hub-252/team-templates-list.md
What team_templates_list does on Hamza Agent Hub 252
AI agents call team_templates_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.
Why team_templates_list is rated Low
Retrieves existing team templates for inspection; no side effects or operations triggered.
From the tool's definition Lists first-party AI-team playbooks and their roles. Does not create or run.
Attacks that exploit this kind of access
The rule that runs team_templates_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_templates_list, this is the rule to start with:
team_templates_list 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 Hamza Agent Hub 252, apply this rule, and every team_templates_list call is checked against it from then on.
Questions about team_templates_list
Lists first-party AI-team playbooks and their roles. Requires team:read. Does not create or run a team. It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for team_templates_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.
team_templates_list 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 team_templates_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.
Set action: deny in the PolicyLayer policy for team_templates_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.
team_templates_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.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue