meta-tools.list_all

List all live Vee3 agent tools. Use this when you need to discover which tools exist and what they are called in MCP. Each entry includes mcp_tool_name, group_id, and summary. Use meta-tools.describe for full request/response schemas and token costs Cost = 0 tokens.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

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-vee3io-vee3/meta-tools.list-all.md

WHAT IT DOES

What meta-tools.list_all does on Vee3

AI agents call meta-tools.list_all 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.

RISK

Why meta-tools.list_all is rated Low

The tool retrieves and lists metadata about available tools on the MCP server. It performs no modifications, deletions, execution, or financial operations. The zero token cost and read-only nature confirm it is informational only. Categorized as Read with low severity due to minimal blast radius—an agent listing available tools poses no direct risk to data or operations.

From the tool's definition Tool name is 'list_all' and description states it 'List[s] all live Vee3 agent tools' with entries including 'mcp_tool_name, group_id, and summary'. This is purely a query/discovery operation with no side effects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meta-tools.list_all 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_all, this is the rule to start with:

meta-tools.list_all Allowed

meta-tools.list_all 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": {
    "meta-tools.list_all": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every meta-tools.list_all call is checked against it from then on.

FAQ

Questions about meta-tools.list_all

What does the meta-tools.list_all tool do? +

How do I enforce a policy on meta-tools.list_all? +

Register the Vee3 MCP server in PolicyLayer and add a rule for meta-tools.list_all: 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.

What risk level is meta-tools.list_all? +

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

Can I rate-limit meta-tools.list_all? +

Yes. Add a rate_limit block to the meta-tools.list_all 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 meta-tools.list_all completely? +

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

meta-tools.list_all 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.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 249 Vee3 tools →

Across the catalogue

The MCP Attack Database →

Guides

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