item_repo

The name of the repository containing the issue or pull request. Required for 'add_project_item' method. (string, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/item-repo.md

WHAT IT DOES

What item_repo does on GitHub

AI agents call item_repo 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.

RISK

Why item_repo is rated Low

This tool appears to be a parameter or accessor for reading/querying repository metadata. While it is used as part of add_project_item operations, the tool itself does not perform write, execute, or destructive actions—it simply identifies or retrieves a repository name. The Read category is appropriate for data retrieval and identification operations.

From the tool's definition Tool description indicates it is a string parameter that specifies 'the name of the repository containing the issue or pull request' for use with 'add_project_item' method.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs item_repo 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_repo, this is the rule to start with:

item_repo Allowed

item_repo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "item_repo": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every item_repo call is checked against it from then on.

FAQ

Questions about item_repo

What does the item_repo tool do? +

The name of the repository containing the issue or pull request. Required for 'add_project_item' method. (string, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on item_repo? +

Register the GitHub MCP server in PolicyLayer and add a rule for item_repo: 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.

What risk level is item_repo? +

item_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit item_repo? +

Yes. Add a rate_limit block to the item_repo 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.

How do I block item_repo completely? +

Set action: deny in the PolicyLayer policy for item_repo. 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.

What MCP server provides item_repo? +

item_repo 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.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →