status_update_id

The node ID of the project status update. Required for 'get_project_status_update' method. (string, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/status-update-id.md

WHAT IT DOES

What status_update_id does on GitHub

AI agents call status_update_id to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why status_update_id is rated Low

This tool is a node ID parameter used to retrieve (get) project status update information from GitHub. It performs data retrieval without modifying, executing, or deleting any resources. The operation is read-only and has minimal security impact, warranting a 'Read' category and 'low' severity classification.

From the tool's definition Tool description indicates this is a parameter for 'get_project_status_update' method, which retrieves project status information. The word 'get' and the context of fetching status updates confirm this is a read operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs status_update_id safely

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

status_update_id Allowed

status_update_id is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "status_update_id": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about status_update_id

What does the status_update_id tool do? +

The node ID of the project status update. Required for 'get_project_status_update' method. (string, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on status_update_id? +

Register the GitHub MCP server in PolicyLayer and add a rule for status_update_id: 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 GitHub. Nothing to install.

What risk level is status_update_id? +

status_update_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit status_update_id? +

Yes. Add a rate_limit block to the status_update_id 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 status_update_id completely? +

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

status_update_id is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →