find_pipeline
AI agents call find_pipeline to retrieve information from Lumino MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a search/retrieval operation ('find') for pipeline objects, typical of observability and debugging workflows. No explicit mutative, destructive, or execution language in the name. However, the empty description limits confidence—the tool could potentially execute queries or trigger pipeline operations if implemented that way.
From the tool's definition Tool name 'find_pipeline' suggests querying or searching for pipeline information. Given the server context (Tekton debugging tools for Kubernetes/OpenShift observability), this likely retrieves pipeline metadata or status data.
Attacks that exploit this kind of access
find_pipeline. It is categorised as a Read tool in the Lumino MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lumino MCP Server MCP server in PolicyLayer and add a rule for find_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 Lumino MCP Server. Nothing to install.
find_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 find_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 find_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.
find_pipeline is provided by the Lumino MCP Server MCP server (lumino-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 →