item_id
The project item ID. Required for 'update_project_item' and 'delete_project_item' methods. (number, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/item-id.md
What item_id does on GitHub
AI agents call item_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 item_id is rated Low
This tool is a data retrieval or reference mechanism—it retrieves or identifies a project item by its ID. It does not perform create, modify, delete, or execute operations on its own; it is merely an identifier used by other methods. The tool name and description indicate it is a parameter for data lookup, not an action with side effects.
From the tool's definition Tool description indicates this is a project item ID parameter used with 'update_project_item' and 'delete_project_item' methods. The tool itself is described as an identifier/parameter (number, optional) rather than an action that performs operations.
Attacks that exploit this kind of access
The rule that runs item_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 item_id, this is the rule to start with:
item_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 item_id call is checked against it from then on.
Questions about item_id
The project item ID. Required for 'update_project_item' and 'delete_project_item' methods. (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 item_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.
item_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 item_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 item_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.
item_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