omg_update_story

Update a story

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/omg-update-story.md

WHAT IT DOES

What omg_update_story does on Gitlab Mcp

AI agents use omg_update_story to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.

RISK

Why omg_update_story is rated Medium

This tool modifies data reversibly by updating an existing story/work item. It is Write rather than Read (retrieves data only) or Destructive (irreversible deletion). Medium severity accounts for the potential to alter project tracking data, though changes are typically reversible via GitLab's audit trail and can be undone by updating again.

From the tool's definition Tool name 'omg_update_story' and description 'Update a story' indicate modification of existing data (a story/work item in GitLab).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs omg_update_story safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For omg_update_story, this is the rule to start with:

omg_update_story Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "omg_update_story": {
      "limits": [
        {
          "counter": "omg_update_story_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every omg_update_story call is checked against it from then on.

FAQ

Questions about omg_update_story

What does the omg_update_story tool do? +

Update a story. It is categorised as a Write tool in the Gitlab Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on omg_update_story? +

Register the Gitlab MCP server in PolicyLayer and add a rule for omg_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 Gitlab Mcp. Nothing to install.

What risk level is omg_update_story? +

omg_update_story is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit omg_update_story? +

Yes. Add a rate_limit block to the omg_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.

How do I block omg_update_story completely? +

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

What MCP server provides omg_update_story? +

omg_update_story is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →