PingOne Privilege

GitHub

The MCP Catalog provides a prebuilt integration for GitHub repositories, issues, and pull requests.

This integration provides:

  • Tools for working with GitHub repositories, issues, and pull requests.

  • Tool, prompt, and resource-level PingOne Privilege policy configuration.

  • Full audit of agent tool calls in Activity > Activity Logs.

Configure a GitHub integration

Configuration involves creating an Github application in PingOne Privilege, configuring policies for the application, and establishing connectivity between the agent and an Agent Privilege gateway.

Before you begin

Ensure you have the following:

  • An AI gateway configured in Directory > Gateways. Learn more in AI gateways.

  • You have a GitHub personal access token or GitHub App with the repository scopes your agents need.

Step 1: Create a GitHub application in PingOne Privilege

  1. In the PingOne Privilege admin console, go to AI Security > Agentic Apps.

  2. Click the MCP Catalog tab.

  3. In the GitHub tile, click Add .

  4. Enter an Application Name for the connection.

  5. Select a Mesh Cluster.

  6. Select an Auth Mode:

    • Static Token: Requires you to provide an Auth Token.

    • User Token: The authorization token will be sourced automatically from the user’s vault credential at request time.

    • None: No authentication will be sent to the MCP server. Use this only if the server is publicly accessible or secured at the network level.

  7. Click Create.

The GitHub integration is now available to AI agents as an MCP server, with PingOne Privilege policy applied to its tools.

Step 2: Configure policies for GitHub tools

  1. In the PingOne Privilege admin console, go to AI Security > Agentic Apps.

  2. In the list, find the GitHub application.

  3. Click (⋮), then click Create Policy.

  4. Select which operations from the GitHub specification are available to agents.

  5. Click Update Configuration.

  6. Add the users or groups the policy will apply to.

  7. Define the users or groups the policy will apply to.

  8. Click Continue.

  9. Configure the policy with the following fields:

    • Policy Name

    • Select Timezone

    • Start Date and Start Time

    • End Date in hours, days, weeks, months, or custom date.

  10. Click Submit to save the policy.

Step 3: Establish connectivity between agent and gateway

  1. In the PingOne Privilege admin console, go to AI Security > Agentic Apps.

  2. On the Active Applications tab, find the GitHub application and click More Info.

  3. On the Overview tab’s Resource Information section, select a configured AI Gateway from the list.

  4. Copy the MCP Config code.

  5. Use the code you just copied to connect to the MCP Catalog app through your client. For example, you can paste the code into Claude Desktop.

    Result: The associated MCP Catalog app is now accessible through that client.

  6. Validate that the GitHub tools appear in the client and that restricted tools don’t appear.

Result

Users can now get the MCP Config for connecting their client to the GitHub app under Agentic Apps in the PingOne Privilege user console.