circleci_list_workflows
List workflows for a CircleCI pipeline.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/circleci-list-workflows.md
What circleci_list_workflows does on UnClick
AI agents call circleci_list_workflows to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | CircleCI personal API token |
pipeline_id | string | Yes | Pipeline ID |
Parameters from the server's own tool schema.
Why circleci_list_workflows is rated Low
This tool retrieves and queries workflow information from CircleCI without modifying, executing, or destroying any data. It is a read-only operation that returns information about existing workflows. The blast radius of misuse is minimal—worst case would be information disclosure of CI/CD pipeline structure, which is typically non-sensitive or already known to project members.
From the tool's definition Tool is named 'circleci_list_workflows' and description states 'List workflows for a CircleCI pipeline.' The verb 'list' is a retrieval operation with no data modification.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs circleci_list_workflows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For circleci_list_workflows, this is the rule to start with:
circleci_list_workflows 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 UnClick, apply this rule, and every circleci_list_workflows call is checked against it from then on.
Questions about circleci_list_workflows
List workflows for a CircleCI pipeline. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
circleci_list_workflows accepts 2 parameters: api_key, pipeline_id. Required: api_key, pipeline_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for circleci_list_workflows: 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 UnClick. Nothing to install.
circleci_list_workflows 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 circleci_list_workflows 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 circleci_list_workflows. 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.
circleci_list_workflows is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue