Skip to main content
Glama

List oidc trust policies

list_oidc_trust_policies
Read-only

List the organisation's GitHub OIDC trust policies (the twin of ankra org oidc-trust list): which repository's workflow runs may exchange their OIDC token for a short-lived Ankra token, narrowed by ref, environment and job_workflow_ref, and the role, scopes and lifetime that token gets. A policy holds no secret. Use it to answer why a workflow's token exchange was refused or what a pipeline's token may do. Read-only; needs members.manage (organisation owners and admins). Creating and deleting a policy are not offered here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_oidc_trust_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description adds real context beyond that: the required permission (members.manage, org owners and admins), the fact that policies contain no secrets, and the exact contents returned (narrowing dimensions and granted role/scopes/lifetime). That is precisely the auth and data-sensitivity information an agent needs before calling.

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

Conciseness4/5

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

Front-loaded with the core verb and resource, and the scoping/diagnostic context follows in short sentences. The opening sentence is dense and the parenthetical CLI twin (`ankra org oidc-trust list`) adds little for an agent, which is the only mild waste.

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

Completeness5/5

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

With no output schema, the description carries the job of explaining what the list returns, and it does so explicitly (repository workflow source, ref/environment/job_workflow_ref narrowing, role, scopes, token lifetime). Authorization requirements are also covered, so nothing an agent needs to call or interpret results correctly is missing.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The prose about ref, environment, job_workflow_ref describes policy contents rather than call inputs, which is appropriate here.

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

Purpose5/5

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

States a specific verb and resource (list the organisation's GitHub OIDC trust policies) and then defines the domain precisely: which repo workflows may exchange an OIDC token, narrowed by ref/environment/job_workflow_ref, and the role/scopes/lifetime granted. It also disambiguates by noting a policy holds no secret, so an agent won't confuse it with a credential-reading tool.

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

Usage Guidelines4/5

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

Gives concrete use cases — diagnosing why a workflow's token exchange was refused, or checking what a pipeline's token may do — plus an explicit exclusion that create/delete are not offered here. It does not name a sibling or other tool where policy creation lives, which keeps it short of a full when/when-not routing statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.