circleci_get_pipeline
Get details for a single CircleCI pipeline by ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/circleci-get-pipeline.md
What circleci_get_pipeline does on UnClick
AI agents call circleci_get_pipeline 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_get_pipeline is rated Low
This tool retrieves pipeline metadata from CircleCI. It is a read-only query operation that returns information about an existing pipeline without creating, modifying, executing, or deleting anything. The blast radius of misuse is minimal - an attacker could learn about CI/CD pipeline structure but cannot execute pipelines, modify configurations, or access secrets stored within them.
From the tool's definition Tool name contains 'get' and description states 'Get details for a single CircleCI pipeline by ID' - purely retrieval operation with no modification or execution capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs circleci_get_pipeline 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_get_pipeline, this is the rule to start with:
circleci_get_pipeline 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_get_pipeline call is checked against it from then on.
Questions about circleci_get_pipeline
Get details for a single CircleCI pipeline by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
circleci_get_pipeline 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_get_pipeline: 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_get_pipeline 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_get_pipeline 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_get_pipeline. 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_get_pipeline 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