mcp-github-enterprise

List security managers

list_security_managers

Read-onlyIdempotent

Identifies teams granted the organization's security-manager role, helping you review least-privilege security triage access and see who can manage security alerts.

Instructions

List the teams granted the organization's security-manager role (least-privilege security triage).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org": "<org>"
    },
    "name": "list_security_managers"
  }
}

Input Schema

Name	Required	Description	Default
`org`	Yes	Organization login (must be within GHE_ORG_ALLOWLIST when that is set)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 7, 2026

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety is fully covered elsewhere. The description adds no behavioral context of its own: no return shape (team objects? member lists?), no note on empty results, and no mention that results depend on the caller's own permissions on the org.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the resource and scope front-loaded and a short parenthetical that earns its place by explaining the role's intent. No redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with rich annotations and a fully documented single parameter, the definition is nearly sufficient. The gap is that the name says 'managers' while the description returns 'teams', leaving the actual response unit (teams vs. individual users) ambiguous, and there is no output schema to resolve it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter and schema coverage is 100%, with the schema itself explaining the org login and the GHE_ORG_ALLOWLIST constraint. The description adds no further meaning about that parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('List the teams granted the organization's security-manager role') and the parenthetical clarifies the role's purpose. It is distinguishable from siblings like list_teams and list_members, though it never explicitly names those alternatives to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for auditing who holds the security-manager role, thanks to 'least-privilege security triage'. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as list_members for non-team-level grants.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.