updated_field
Object consisting of the ID of the project field to update and the new value for the field. To clear the field, set value to null. Example: {"id": 123456, "value": "New Value"}. Required for 'update_project_item' method. (object, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/updated-field.md
What updated_field does on GitHub
AI agents call updated_field as a supporting operation in GitHub workflows.
Why updated_field is rated Low
This appears to be a parameter descriptor or schema definition for the 'update_project_item' method rather than an independently callable tool. It has no executable action of its own; it merely describes the shape of data to pass to another operation. Classifying as Other with low confidence due to the ambiguous and uninformative description that doesn't describe an invokable action.
From the tool's definition 'Object consisting of the ID of the project field to update and the new value for the field' — this describes a parameter/input object, not a standalone tool with executable behavior.
Attacks that exploit this kind of access
The rule that runs updated_field 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 updated_field, this is the rule to start with:
updated_field gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every updated_field call is checked against it from then on.
Questions about updated_field
Object consisting of the ID of the project field to update and the new value for the field. To clear the field, set value to null. Example: {"id": 123456, "value": "New Value"}. Required for 'update_project_item' method. (object, optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.
Register the GitHub MCP server in PolicyLayer and add a rule for updated_field: 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.
updated_field is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the updated_field 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 updated_field. 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.
updated_field 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue