circleci_get_workflow
Get details for a single CircleCI workflow by ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/circleci-get-workflow.md
What circleci_get_workflow does on UnClick
AI agents call circleci_get_workflow 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 |
workflow_id | string | Yes | Workflow ID |
Parameters from the server's own tool schema.
Why circleci_get_workflow is rated Low
This tool retrieves workflow information from CircleCI by querying a workflow ID. It performs a read-only operation that returns existing data without creating, modifying, deleting, or executing any actions. The action is informational only, making it a Read category tool with low severity since it does not expose sensitive data operations or system controls.
From the tool's definition Tool description states 'Get details for a single CircleCI workflow by ID' - uses 'Get' which indicates data retrieval without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs circleci_get_workflow 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_workflow, this is the rule to start with:
circleci_get_workflow 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_workflow call is checked against it from then on.
Questions about circleci_get_workflow
Get details for a single CircleCI workflow by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
circleci_get_workflow accepts 2 parameters: api_key, workflow_id. Required: api_key, workflow_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_workflow: 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_workflow 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_workflow 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_workflow. 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_workflow 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