Ignoring an Aikido PR finding via an @AikidoSec ignore reply - and the 400 feature-disabled error

Per the Aikido workflow notes: ignore PR findings with @AikidoSec ignore: on the finding thread; a 400 means the workspace MCP ignore permission is disabled.

Context: Problem: Aikido flagged a false positive on a pull request. Reply on that finding comment thread with a message starting "@AikidoSec ignore:" followed by the ignore reason. Via the MCP server, call the ignore tool with the issue_id from the feed and the reason. If the MCP call returns "400 - Feature is disabled for this workspace", the workspace MCP ignore permission is off - point an Aikido admin at the MCP permissions settings page to enable it, and fall back to ignoring the issue manually in the UI in the meantime.

Matched source

Source: Source: https://github.com/lifinance/contracts/blob/HEAD/.agents/commands/aikido-address-findings.md Original query: "Ignoring an Aikido PR finding via an @AikidoSec ignore reply - and the 400 feature-disabled error" Key terms: aikido, aikidosec, disabled, error, feature, finding, ignore, ignoring, reply

Source: Problem: Aikido flagged a false positive on a pull request. Reply on that finding comment thread with a message starting "@AikidoSec ignore:" followed by the ignore reason. Via the MCP server, call the ignore tool with the issue_id from the feed and the reason. If the MCP call returns "400 - Feature is disabled for this workspace", the workspace MCP ignore permission is off - point an Aikido admin at the MCP permissions settings page to enable it, and fall back to ignoring the issue manually in the UI in the meantime.

Verified resolution: Per the Aikido workflow notes: ignore PR findings with @AikidoSec ignore: on the finding thread; a 400 means the workspace MCP ignore permission is disabled.

Source URL: https://github.com/lifinance/contracts/blob/HEAD/.agents/commands/aikido-address-findings.md