report_company_bug
Log a bug reported by a company: creates a board bug (FBB-###), links it to the company, and records the report on the company. Ties customer reports to the bug workflow.
This record as markdown: /tools/ai-featureboard-featureboard/report-company-bug.md
What report_company_bug does on FeatureBoard
AI agents use report_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.
Why report_company_bug is rated Medium
This tool creates new bug records and modifies company records by linking and recording information. These are write operations that create new data structures and establish associations. While the data creation is permanent, bugs can be closed, records can be unlinked, and the operation is not destructive or financial in nature.
From the tool's definition Tool description states it 'creates a board bug (FBB-###), links it to the company, and records the report on the company' — all create/modify operations with reversible effects.
Attacks that exploit this kind of access
The rule that runs report_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 report_company_bug, this is the rule to start with:
report_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.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every report_company_bug call is checked against it from then on.
Questions about report_company_bug
Log a bug reported by a company: creates a board bug (FBB-###), links it to the company, and records the report on the company. Ties customer reports to the bug workflow. 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.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for report_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.
report_company_bug is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the report_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.
Set action: deny in the PolicyLayer policy for report_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.
report_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.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue