list CI pipelines for a repository
AI agents call list_pipelines to retrieve information from Tangled MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing CI pipeline information. It performs no mutations, does not execute code or pipelines, and does not delete or modify data. The 'list' verb and passive retrieval nature are characteristic of Read category operations.
From the tool's definition Tool name 'list_pipelines' and description 'list CI pipelines for a repository' indicate a read-only query operation that retrieves pipeline information without modifying, executing, or deleting data.
Attacks that exploit this kind of access
list CI pipelines for a repository. It is categorised as a Read tool in the Tangled MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tangled MCP Server MCP server in PolicyLayer and add a rule for 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 Tangled MCP Server. Nothing to install.
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 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 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.
list_pipelines is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_pipelines is one line of Tangled MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →