resource_id
The unique identifier of the resource. This will vary based on the "method" provided, so ensure you provide the correct ID:
This record as markdown: /tools/io-github-aifity-omnigit-mcp/resource-id.md
What resource_id does on GitHub
AI agents call resource_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 resource_id is rated Low
This is a utility tool that retrieves or returns resource identifiers without side effects. It does not modify, delete, or execute operations. While it's part of a GitHub management system, the tool itself only performs a Read operation - providing unique identifiers for resources. No destructive, financial, or executable actions are described.
From the tool's definition Tool description states it provides 'The unique identifier of the resource' - a retrieval/lookup function with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs resource_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 resource_id, this is the rule to start with:
resource_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 resource_id call is checked against it from then on.
Questions about resource_id
The unique identifier of the resource. This will vary based on the "method" provided, so ensure you provide the correct ID:. 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 resource_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.
resource_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 resource_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 resource_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.
resource_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