append_research
Capture ONE research finding into a ticket
This record as markdown: /tools/ai-featureboard-featureboard/append-research.md
What append_research does on FeatureBoard
AI agents use append_research 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 append_research is rated Medium
This tool creates or adds research findings to a ticket, modifying the ticket's content in a reversible manner. This is a Write operation with minimal blast radius—the worst case is incorrect research being added to a ticket, which can be undone by editing or removing the entry. No financial impact, no irreversible deletion, no code execution, and no destructive action is implied.
From the tool's definition Tool name 'append_research' and description 'Capture ONE research finding into a ticket' indicates adding data to a ticket without deletion or modification of existing content. The word 'append' explicitly means adding data reversibly.
Attacks that exploit this kind of access
The rule that runs append_research 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 append_research, this is the rule to start with:
append_research 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 append_research call is checked against it from then on.
Questions about append_research
Capture ONE research finding into a ticket. 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 append_research: 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.
append_research 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 append_research 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 append_research. 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.
append_research 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