meta-tools.request_feature

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

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/meta-tools.request-feature.md

WHAT IT DOES

What meta-tools.request_feature does on Vee3

AI agents use meta-tools.request_feature to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.

Parameter	Type	Required	Description
`summary`	string	Yes	Short title describing the requested capability or feature.
`use_case`	object	—	Example workflow or scenario where this feature would be used.
`description`	string	Yes	Detailed explanation of what is needed, why it cannot be done with existing tools, and how it would help.
`related_capability_id`	object	—	Capability id this request extends or relates to, if applicable.

Parameters from the server's own tool schema.

RISK

Why meta-tools.request_feature is rated Medium

This tool submits a feature request, which is a write operation (creating a new request/record in some system). It has no destructive, financial, or execution implications. The blast radius of misuse is low — at worst it spams feature requests.

From the tool's definition Request a new capability or feature that Vee3 does not offer yet

Attacks that exploit this kind of access

RECOMMENDED RULE

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

meta-tools.request_feature Rate-limited

meta-tools.request_feature stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta-tools.request_feature": {
      "limits": [
        {
          "counter": "meta-tools.request_feature_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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.request_feature call is checked against it from then on.

FAQ

Questions about meta-tools.request_feature

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

Request a new capability or feature that Vee3 does not offer yet. Use this when you need something that is not available in the catalog — a missing integration, data source, workflow, or enhancement to an existing capability. Describe what you need, why you cannot accomplish it today, and how you would use it Cost = 0 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does meta-tools.request_feature accept? +

meta-tools.request_feature accepts 4 parameters: summary, use_case, description, related_capability_id. Required: summary, description. The full parameter table on this page comes from the server's own tool schema.

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

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

meta-tools.request_feature is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

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

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

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

Govern customer-ops agents →Argument validation →Scoped token →