meta-tools.list_groups
List all Vee3 capability groups. Use this to see how tools are organized (for example website-screenshots or meta-tools) before listing tools in a specific group Cost = 0 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/meta-tools.list-groups.md
What meta-tools.list_groups does on Vee3
AI agents call meta-tools.list_groups 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.
Why meta-tools.list_groups is rated Low
This tool retrieves and displays organizational metadata about available capability groups on the Vee3 server. It performs a query operation with no ability to modify, execute, delete, or commit financial actions. The zero token cost and informational purpose confirm it is a low-severity read operation.
From the tool's definition Tool name is 'list_groups' and description states it 'List[s] all Vee3 capability groups' to 'see how tools are organized'. This is a read-only operation that retrieves metadata about tool organization with no side effects.
Attacks that exploit this kind of access
The rule that runs meta-tools.list_groups 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_groups, this is the rule to start with:
meta-tools.list_groups 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_groups call is checked against it from then on.
Questions about meta-tools.list_groups
List all Vee3 capability groups. Use this to see how tools are organized (for example website-screenshots or meta-tools) before listing tools in a specific group Cost = 0 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
Register the Vee3 MCP server in PolicyLayer and add a rule for meta-tools.list_groups: 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_groups 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_groups 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_groups. 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_groups 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