add_decision
Append a new ADR to a project
This record as markdown: /tools/ai-featureboard-featureboard/add-decision.md
What add_decision does on FeatureBoard
AI agents use add_decision 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 add_decision is rated Medium
This tool creates new decision records in the project board by appending data. It is a Write operation because it creates new data structures (ADRs) without permanent deletion or financial impact. Severity is medium because adding decisions could mislead project planning or create confusion if done incorrectly, but the action is reversible and localized to project documentation.
From the tool's definition Tool name 'add_decision' and description 'Append a new ADR to a project' indicate creating/adding new decision records (ADR = Architecture Decision Record) to a project, which modifies project data reversibly.
Attacks that exploit this kind of access
The rule that runs add_decision 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 add_decision, this is the rule to start with:
add_decision 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 add_decision call is checked against it from then on.
Questions about add_decision
Append a new ADR to a project. 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 add_decision: 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.
add_decision 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 add_decision 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 add_decision. 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.
add_decision 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