list_github_api_calls_in_run

List every HTTPS call to github.com or api.github.com made by jobs in a specific workflow run. Useful for auditing which GitHub API endpoints a workflow touches — detecting writes to unexpected repos, surprising org access, or API calls from third-party Actions. Fast: one upstream API call. Requi...

Server Stepsecurity step-security/stepsecurity-mcp
Category Read
Risk class Low
Parameters 00 required

What list_github_api_calls_in_run does on Stepsecurity

AI agents call list_github_api_calls_in_run to retrieve information from Stepsecurity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_github_api_calls_in_run needs a policy

Even though list_github_api_calls_in_run only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about list_github_api_calls_in_run

What does the list_github_api_calls_in_run tool do? +

List every HTTPS call to github.com or api.github.com made by jobs in a specific workflow run. Useful for auditing which GitHub API endpoints a workflow touches — detecting writes to unexpected repos, surprising org access, or API calls from third-party Actions. Fast: one upstream API call. Requires a run_id — if the user doesn. It is categorised as a Read tool in the Stepsecurity MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_github_api_calls_in_run? +

Register the Stepsecurity MCP server in PolicyLayer and add a rule for list_github_api_calls_in_run: 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 Stepsecurity. Nothing to install.

What risk level is list_github_api_calls_in_run? +

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

Can I rate-limit list_github_api_calls_in_run? +

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

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

list_github_api_calls_in_run is provided by the Stepsecurity MCP server (step-security/stepsecurity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.