snow_agile_story_manage
Create and update user stories in ServiceNow Agile 2.0. Assign story points, link to sprints/epics, manage acceptance criteria, and update state.
This record as markdown: /tools/serac/snow-agile-story-manage.md
What snow_agile_story_manage does on Serac
AI agents use snow_agile_story_manage to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_agile_story_manage is rated Medium
This tool creates and modifies user stories, sprints, epics, and acceptance criteria—core project data. While reversible (Write, not Destructive), the scope is broad: it can alter sprint planning, story assignments, and workflow state across an enterprise system. Misuse by an AI agent could corrupt agile planning, mislead teams on project status, or artificially inflate/deflate story points.
From the tool's definition Tool description states 'Create and update user stories' and 'update state', indicating reversible modification of project management data in ServiceNow.
Attacks that exploit this kind of access
The rule that runs snow_agile_story_manage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_agile_story_manage, this is the rule to start with:
snow_agile_story_manage 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 Serac, apply this rule, and every snow_agile_story_manage call is checked against it from then on.
Questions about snow_agile_story_manage
Create and update user stories in ServiceNow Agile 2.0. Assign story points, link to sprints/epics, manage acceptance criteria, and update state. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_agile_story_manage: 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 Serac. Nothing to install.
snow_agile_story_manage 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 snow_agile_story_manage 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 snow_agile_story_manage. 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.
snow_agile_story_manage is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue