Get the list of sprints in Plan for a given application
AI agents call get_sprints to retrieve information from MCP DevOps Plan Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves sprint data for a specified application. It performs a read-only operation that returns information without modifying, creating, or deleting any data. The action is consistent with the 'Read' category: retrieves or queries data with no side effects. Severity is low because retrieving sprint metadata poses minimal risk even if an AI agent calls it unexpectedly.
From the tool's definition Tool name 'get_sprints' and description 'Get the list of sprints in Plan for a given application' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the list of sprints in Plan for a given application. It is categorised as a Read tool in the MCP DevOps Plan Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DevOps Plan Server MCP server in PolicyLayer and add a rule for get_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 MCP DevOps Plan Server. Nothing to install.
get_sprints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_sprints is provided by the MCP DevOps Plan Server MCP server (mrchris2000/mcp-devops-plan). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →