repair_duplicate_ids
Find ticket ids that appear more than once on a board (legacy data can carry collisions like FBF-491 twice),
This record as markdown: /tools/ai-featureboard-featureboard/repair-duplicate-ids.md
What repair_duplicate_ids does on FeatureBoard
AI agents use repair_duplicate_ids 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 repair_duplicate_ids is rated Medium
This tool modifies board data by repairing/fixing duplicate IDs, which is a reversible write operation. It doesn't delete data irreversibly (not Destructive), nor does it execute arbitrary code (not Execute). It's more intrusive than a Read operation since it alters state.
From the tool's definition Tool name is 'repair_duplicate_ids' and description indicates it finds and addresses duplicate ticket IDs in board data. The term 'repair' suggests modification of board state to resolve collisions.
Attacks that exploit this kind of access
The rule that runs repair_duplicate_ids 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 repair_duplicate_ids, this is the rule to start with:
repair_duplicate_ids 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 repair_duplicate_ids call is checked against it from then on.
Questions about repair_duplicate_ids
Find ticket ids that appear more than once on a board (legacy data can carry collisions like FBF-491 twice),. 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 repair_duplicate_ids: 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.
repair_duplicate_ids 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 repair_duplicate_ids 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 repair_duplicate_ids. 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.
repair_duplicate_ids 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