create_sprint
Create (or update) a named sprint on a board, with optional start/end dates and a one-line goal.
This record as markdown: /tools/ai-featureboard-featureboard/create-sprint.md
What create_sprint does on FeatureBoard
AI agents use create_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 create_sprint is rated Medium
This tool creates or modifies sprint data on a project board, which is a write operation. It has no destructive capability (sprints are not deleted), does not execute code or external operations, and involves no financial transactions. The severity is medium because misuse could affect project planning and timeline visibility, but the impact is scoped to the board's sprint data and remains reversible.
From the tool's definition Tool name is 'create_sprint' and description states it can 'Create (or update) a named sprint' — explicitly a create and modify operation. The action is reversible (sprints can be updated or deleted later).
Attacks that exploit this kind of access
The rule that runs create_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 create_sprint, this is the rule to start with:
create_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 create_sprint call is checked against it from then on.
Questions about create_sprint
Create (or update) a named sprint on a board, with optional start/end dates and a one-line goal. 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 create_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.
create_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 create_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 create_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.
create_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