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

TL;DR

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.

Steps

1. 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.

When to use

You are seeing this: Reply on that finding comment thread with a message starting "@AikidoSec ignore:" followed by the ignore reason. Use this skill when you run into "Ignoring an Aikido PR finding via an @AikidoSec ignore reply - and the 400 feature-disabled error".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

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