resolve_company_bug

Mark a company-reported bug resolved: sets the board bug to Done and flips the company

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/resolve-company-bug.md

WHAT IT DOES

What resolve_company_bug does on FeatureBoard

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

RISK

Why resolve_company_bug is rated Medium

This tool modifies existing data (bug status and company field) but does not irreversibly delete data. The changes are reversible—a bug marked Done can be reopened, and the company flip can be toggled back. This fits Write rather than Destructive. Severity is medium because misuse could incorrectly close bug records or corrupt CRM relationships, but the harm is bounded by reversal potential.

From the tool's definition Tool description states: 'Mark a company-reported bug resolved: sets the board bug to Done and flips the company'. The verb 'Mark' and 'sets' indicate modification of data state (bug status to 'Done').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs resolve_company_bug safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resolve_company_bug, this is the rule to start with:

resolve_company_bug Rate-limited

resolve_company_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": {
    "resolve_company_bug": {
      "limits": [
        {
          "counter": "resolve_company_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 FeatureBoard, apply this rule, and every resolve_company_bug call is checked against it from then on.

FAQ

Questions about resolve_company_bug

What does the resolve_company_bug tool do? +

Mark a company-reported bug resolved: sets the board bug to Done and flips the company. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_company_bug? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for resolve_company_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 FeatureBoard. Nothing to install.

What risk level is resolve_company_bug? +

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

Can I rate-limit resolve_company_bug? +

Yes. Add a rate_limit block to the resolve_company_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 resolve_company_bug completely? +

Set action: deny in the PolicyLayer policy for resolve_company_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 resolve_company_bug? +

resolve_company_bug is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

resolve_circuit on 0gzk → The MCP Attack Database →

Guides

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