This record as markdown: /tools/io-github-portel-dev-ncp/list-workflow-runs.md
What list_workflow_runs does on Ncp
AI agents call list_workflow_runs to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_workflow_runs is rated Low
This tool retrieves and lists workflow run data from GitHub Actions. It performs a query operation with no side effects, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an agent could retrieve workflow information but cannot execute workflows, delete them, or modify CI/CD pipelines. This is a straightforward Read operation.
From the tool's definition Tool name 'list_workflow_runs' and description 'List GitHub Actions workflow runs' indicate a retrieval operation that queries workflow execution history without modifying data.
Attacks that exploit this kind of access
The rule that runs list_workflow_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workflow_runs, this is the rule to start with:
list_workflow_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every list_workflow_runs call is checked against it from then on.
Questions about list_workflow_runs
List GitHub Actions workflow runs. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp MCP server in PolicyLayer and add a rule for list_workflow_runs: 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 Ncp. Nothing to install.
list_workflow_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_workflow_runs 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.
Set action: deny in the PolicyLayer policy for list_workflow_runs. 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.
list_workflow_runs is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue