assign_sprint
Move one or more tickets into a sprint — sets the sprint:<name> label, replacing any existing sprint label.
This record as markdown: /tools/ai-featureboard-featureboard/assign-sprint.md
What assign_sprint does on FeatureBoard
AI agents use assign_sprint 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 assign_sprint is rated Medium
The tool creates or modifies data (ticket sprint assignments via labels) in a reversible manner. Sprint assignments can be changed or removed without permanent loss. This is a Write-class operation rather than Destructive since label changes are not irreversible.
From the tool's definition Tool description states it "Move[s] one or more tickets into a sprint — sets the sprint:<name> label, replacing any existing sprint label." This modifies ticket metadata (labels) reversibly.
Attacks that exploit this kind of access
The rule that runs assign_sprint 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 assign_sprint, this is the rule to start with:
assign_sprint 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 assign_sprint call is checked against it from then on.
Questions about assign_sprint
Move one or more tickets into a sprint — sets the sprint:<name> label, replacing any existing sprint label. 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 assign_sprint: 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.
assign_sprint 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 assign_sprint 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 assign_sprint. 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.
assign_sprint 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