fields
Field IDs to include when listing project items (e.g. ["102589", "985201"]). CRITICAL: Always provide to get field values. Without this, only titles returned. Only used for 'list_project_items' method. (string[], optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/fields.md
What fields does on GitHub
AI agents call fields 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 fields is rated Low
This tool is a configuration parameter for a read operation (listing project items with specific fields). It retrieves data without side effects. The 'CRITICAL' label in the description refers to the importance of providing the parameter to get complete results, not to security severity.
From the tool's definition Tool description states 'Field IDs to include when listing project items' and is 'Only used for list_project_items method.' This is a parameter that filters or specifies which fields to retrieve when querying project items, not an action that modifies,…
Attacks that exploit this kind of access
The rule that runs fields 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 fields, this is the rule to start with:
fields 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 fields call is checked against it from then on.
Questions about fields
Field IDs to include when listing project items (e.g. ["102589", "985201"]). CRITICAL: Always provide to get field values. Without this, only titles returned. Only used for 'list_project_items' method. (string[], 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 fields: 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.
fields 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 fields 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 fields. 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.
fields 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