field_id
The field's ID. Required for 'get_project_field' method. (number, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/field-id.md
What field_id does on GitHub
AI agents call field_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.
Why field_id is rated Low
This tool is a parameter/identifier used in lookup operations (get_project_field), not an action that modifies, executes, or deletes data. The Read category applies to retrieval operations. The severity is low because exposing a field identifier for queries has minimal blast radius — it only retrieves data already accessible through the GitHub API.
From the tool's definition field_id is described as 'The field's ID. Required for 'get_project_field' method' — it is a parameter that identifies a field for retrieval, supporting a 'get' operation which is a Read action.
Attacks that exploit this kind of access
The rule that runs field_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 field_id, this is the rule to start with:
field_id is read-only, so it stays allowed. 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 field_id call is checked against it from then on.
Questions about field_id
The field's ID. Required for 'get_project_field' method. (number, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for field_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.
field_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the field_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.
Set action: deny in the PolicyLayer policy for field_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.
field_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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue