AI agents call get_velocity_forecast to retrieve information from Scrumdo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns predictive metadata about a card's estimated completion timeline. It has no side effects, does not modify board state, execute external operations, or move data irreversibly. It is a pure read operation that retrieves or computes information for display purposes.
From the tool's definition Tool name is 'get_velocity_forecast' and description states it returns a 'Predicted cycle-time band for a card at its current complexity.' The verb 'get' combined with 'forecast' (a computed prediction) and the absence of any modification, deletion, or…
Attacks that exploit this kind of access
Predicted cycle-time band for a card at its current complexity. It is categorised as a Read tool in the Scrumdo MCP Server, which means it retrieves data without modifying state.
Register the Scrumdo MCP server in PolicyLayer and add a rule for get_velocity_forecast: 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 Scrumdo. Nothing to install.
get_velocity_forecast 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_velocity_forecast 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_velocity_forecast. 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_velocity_forecast is provided by the Scrumdo MCP server (scrumdollc/scrumdo-mcp). 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 →