meta-tools.describe
Describe a single Vee3 capability. Pass the MCP tool name (for example website-screenshots.capture) or capability id (for example website-screenshot). Use this after meta-tools.list_group_tools when you need parameter names, defaults, response fields, examples, and token cost before calling a too...
This record as markdown: /tools/io-github-vee3io-vee3/meta-tools.describe.md
What meta-tools.describe does on Vee3
AI agents call meta-tools.describe 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 |
|---|---|---|---|
tool_name | string | Yes | MCP tool name (for example `x-twitter.create_post`) or capability id (for example `create-x-post`). |
Parameters from the server's own tool schema.
Why meta-tools.describe is rated Low
This is a metadata/documentation retrieval tool that queries information about other tools' capabilities. It has no side effects, creates no changes, executes no code, and poses minimal risk. It is squarely in the Read category as it only retrieves and returns descriptive information.
From the tool's definition Tool name and description indicate it 'Describe a single Vee3 capability' and retrieves 'parameter names, defaults, response fields, examples, and token cost' - purely informational retrieval with no data modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs meta-tools.describe 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.describe, this is the rule to start with:
meta-tools.describe 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.describe call is checked against it from then on.
Questions about meta-tools.describe
Describe a single Vee3 capability. Pass the MCP tool name (for example website-screenshots.capture) or capability id (for example website-screenshot). Use this after meta-tools.list_group_tools when you need parameter names, defaults, response fields, examples, and token cost before calling a tool 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.describe accepts 1 parameter: tool_name. Required: tool_name. 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.describe: 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.describe 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.describe 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.describe. 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.describe 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