team_slug

Team slug (string, required)

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/team-slug.md

WHAT IT DOES

What team_slug does on GitHub

AI agents call team_slug 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 team_slug is rated Low

This tool provides a team slug identifier used to look up or reference team data. It is a lookup/retrieval mechanism with no modification, execution, or deletion capability. The low severity reflects minimal blast radius if misused - it only returns team identification information.

From the tool's definition Tool named 'team_slug' that appears to be a parameter identifier for retrieving team information - it accepts a string identifier and is listed among Read operations like 'actions_list' and 'actions_get'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

team_slug Allowed

team_slug 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": {
    "team_slug": {}
  }
}

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 team_slug call is checked against it from then on.

FAQ

Questions about team_slug

What does the team_slug tool do? +

Team slug (string, required). 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 team_slug? +

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

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

Can I rate-limit team_slug? +

Yes. Add a rate_limit block to the team_slug 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 team_slug completely? +

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

team_slug 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

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

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