list_sprints

List a board

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/list-sprints.md

WHAT IT DOES

What list_sprints does on FeatureBoard

AI agents call list_sprints to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_sprints is rated Low

This is a straightforward read operation that retrieves sprint information from a project board. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an AI agent listing sprints cannot cause harm beyond potentially viewing information it shouldn't access, which is a read-level concern.

From the tool's definition Tool name 'list_sprints' and description 'List a board' indicate a retrieval operation with no side effects. This queries existing sprint/board data without modifying, deleting, or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_sprints 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 list_sprints, this is the rule to start with:

list_sprints Allowed

list_sprints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_sprints": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every list_sprints call is checked against it from then on.

FAQ

Questions about list_sprints

What does the list_sprints tool do? +

List a board. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_sprints? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for list_sprints: 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.

What risk level is list_sprints? +

list_sprints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_sprints? +

Yes. Add a rate_limit block to the list_sprints 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.

How do I block list_sprints completely? +

Set action: deny in the PolicyLayer policy for list_sprints. 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.

What MCP server provides list_sprints? +

list_sprints 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.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →