AI agents call circleci_list_pipelines to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
branch | string | — | Filter by branch name |
api_key | string | Yes | CircleCI personal API token |
org_slug | string | — | Org slug when listing all pipelines (e.g. gh/MyOrg) |
page_token | string | — | Pagination token |
project_slug | string | — | Project slug e.g. gh/MyOrg/my-repo. Omit to list all org pipelines. |
Parameters from the server's own tool schema.
This tool retrieves and queries existing CircleCI pipeline data. It performs a lookup/list operation with optional filtering parameters, which are characteristic of Read operations. There is no modification, deletion, execution of pipelines, or financial impact. The read-only retrieval of pipeline metadata poses minimal risk to system integrity.
From the tool's definition Tool name includes 'list' and description states 'List CircleCI pipelines for a project or organization. Optionally filter by branch.' The verb 'list' and the read-only nature of querying pipeline information with optional filtering indicates data retrieval…
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List CircleCI pipelines for a project or organization. Optionally filter by branch. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
circleci_list_pipelines accepts 5 parameters: branch, api_key, org_slug, page_token, project_slug. Required: api_key. 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_pipelines: 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_pipelines 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_pipelines 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_pipelines. 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_pipelines 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →