meta-tools.list_group_tools
List live tools belonging to a single capability group. Use group_id from meta-tools.list_groups (for example website-screenshots). Returns name and summary for each live tool in the group Cost = 0 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/meta-tools.list-group-tools.md
What meta-tools.list_group_tools does on Vee3
AI agents call meta-tools.list_group_tools to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
group_id | string | Yes | Group id to list tools for (for example website-screenshots). |
Parameters from the server's own tool schema.
Why meta-tools.list_group_tools is rated Low
This is a metadata query operation that retrieves information about available tools in a group. It has no side effects, does not execute code or commands, and does not modify any data. The zero token cost further supports this is a simple informational lookup. Classified as Read with low severity due to negligible blast radius if misused by an agent.
From the tool's definition Tool name contains 'list' and description states it 'List live tools belonging to a single capability group' and 'Returns name and summary for each live tool'. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs meta-tools.list_group_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meta-tools.list_group_tools, this is the rule to start with:
meta-tools.list_group_tools 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 Vee3, apply this rule, and every meta-tools.list_group_tools call is checked against it from then on.
Questions about meta-tools.list_group_tools
List live tools belonging to a single capability group. Use group_id from meta-tools.list_groups (for example website-screenshots). Returns name and summary for each live tool in the group Cost = 0 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
meta-tools.list_group_tools accepts 1 parameter: group_id. Required: group_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for meta-tools.list_group_tools: 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 Vee3. Nothing to install.
meta-tools.list_group_tools 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 meta-tools.list_group_tools 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 meta-tools.list_group_tools. 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.
meta-tools.list_group_tools is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue