update_story
Update an agile story (requires WRITE_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/update-story.md
What update_story does on ServiceNow MCP Server
AI agents use update_story to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why update_story is rated Medium
This tool creates or modifies data reversibly by updating agile story records in ServiceNow. It is a Write category tool because it changes existing data without permanent destruction. Severity is medium because unauthorized updates to agile stories could disrupt project planning and team workflows, but the changes are reversible and do not affect financial systems or permanently delete data.
From the tool's definition Tool name is 'update_story' and description states 'Update an agile story' — core Write operation. Requires explicit WRITE_ENABLED=true flag, indicating controlled modification capability.
Attacks that exploit this kind of access
The rule that runs update_story safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_story, this is the rule to start with:
update_story 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 ServiceNow MCP Server, apply this rule, and every update_story call is checked against it from then on.
Questions about update_story
Update an agile story (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for update_story: 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 ServiceNow MCP Server. Nothing to install.
update_story 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 update_story 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 update_story. 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.
update_story is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue