New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_sprint_report

Read the close-out reports written by close_sprint. With no sprint: list sprints that have reports. With a sprint but no audience: the manifest + which audiences exist. With sprint + audience (marketing|sales|technical|executive): that report

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/get-sprint-report.md

What get_sprint_report does on FeatureBoard

AI agents call get_sprint_report 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.

Why get_sprint_report is rated Low

This tool only retrieves and queries existing sprint reports and metadata. It has no side effects, cannot modify data, and simply returns information in different formats based on query parameters. The highest impact would be unauthorized information access, which is a typical read operation risk.

From the tool's definition Tool name contains 'get_' prefix and description explicitly states 'Read the close-out reports' and 'list sprints'. The operations are pure queries: listing available sprints, fetching manifests, and retrieving pre-written reports with no data modification.

Questions about get_sprint_report

What does the get_sprint_report tool do? +

Read the close-out reports written by close_sprint. With no sprint: list sprints that have reports. With a sprint but no audience: the manifest + which audiences exist. With sprint + audience (marketing|sales|technical|executive): that report. 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 get_sprint_report? +

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

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

Can I rate-limit get_sprint_report? +

Yes. Add a rate_limit block to the get_sprint_report 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 get_sprint_report completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FeatureBoard's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.