log_bug

Log a bug to a board

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/log-bug.md

WHAT IT DOES

What log_bug does on FeatureBoard

AI agents use log_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 log_bug is rated Medium

The tool creates a new bug entry in the board, which is a reversible modification of data (bugs can be edited, closed, or deleted). This is Write category rather than Execute because it doesn't run code or trigger external operations—it simply records information.

From the tool's definition Tool name 'log_bug' and description 'Log a bug to a board' indicate creation of a new bug record in the project board system. This is a write operation that creates data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log_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 log_bug, this is the rule to start with:

log_bug Rate-limited

log_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": {
    "log_bug": {
      "limits": [
        {
          "counter": "log_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 log_bug call is checked against it from then on.

FAQ

Questions about log_bug

What does the log_bug tool do? +

Log a bug to a board. 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 log_bug? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for log_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 log_bug? +

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

Can I rate-limit log_bug? +

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

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

log_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

The MCP Attack Database →

Guides

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