meta-tools.report_bug

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.report-bug.md

WHAT IT DOES

What meta-tools.report_bug does on Vee3

AI agents use meta-tools.report_bug 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 issue.
`description`	string	Yes	Detailed explanation of what went wrong, what was expected, and steps to reproduce if known.
`error_details`	object	—	Raw error message, stack trace, or API response that shows the failure.
`related_capability_id`	object	—	MCP tool name or capability id involved in the issue, if applicable.

Parameters from the server's own tool schema.

RISK

Why meta-tools.report_bug is rated Medium

This tool sends a bug report to Vee3, which is a write operation (creates a new report entry). It has no destructive, financial, or code-execution capabilities. The blast radius of misuse is low — at worst, spam reports are submitted.

From the tool's definition 'Report a bug, error, or anything that did not work as expected' — this submits a report/feedback, creating a new record on the server side

Attacks that exploit this kind of access

RECOMMENDED RULE

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

meta-tools.report_bug Rate-limited

meta-tools.report_bug 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.report_bug": {
      "limits": [
        {
          "counter": "meta-tools.report_bug_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.report_bug call is checked against it from then on.

FAQ

Questions about meta-tools.report_bug

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

Report a bug, error, or anything that did not work as expected while using Vee3. Use this when a capability fails unexpectedly, returns wrong data, or behaves inconsistently. Include what you tried, what happened, and any error output 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.report_bug accept? +

meta-tools.report_bug accepts 4 parameters: summary, description, error_details, 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.report_bug? +

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

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

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

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

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

meta-tools.report_bug 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 →