GitHub Actions Permission Auditor
Pricing
from $4.90 / 1,000 page auditeds
Audit GitHub Actions workflow YAML files for token permission scope, risky triggers, third-party action pinning, secret usage patterns, OIDC configuration, and workflow-level permission hardening.
You can access the GitHub Actions Permission Auditor programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/github-actions-permission-auditor" } }}The configuration above connects to the hosted Apify MCP server with the GitHub Actions Permission Auditor — technical SEO, web, and Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the GitHub Actions Permission Auditor — technical SEO, web, and Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,junipr/github-actions-permission-auditor.
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.