# run_pipeline Execute a data pipeline Agent View of the PolicyLayer registry record for `run_pipeline`. HTML page: https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/run-pipeline ## Facts - Tool: `run_pipeline` - Server: Claude MCP Server Ecosystem (`coder-rl/claude_mcpserver_dev1`) — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1.md - Homepage: https://github.com/Coder-RL/Claude_MCPServer_Dev1 - Risk category: Execute (High risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "run_pipeline", "arguments": {} } } ``` ## Why run_pipeline is rated High Pipelines are orchestrated workflows that can trigger multiple operations across systems, run scripts, query databases, and invoke external services. The blast radius depends entirely on what the pipeline is configured to do—it could modify data, trigger infrastructure changes, or call external APIs. Without constraints on pipeline definition, a compromised agent could execute arbitrary operations. From the tool's own definition: "Tool name 'run_pipeline' with description 'Execute a data pipeline' indicates execution of a potentially complex, multi-stage operation." ## Use case AI agents invoke run_pipeline to trigger actions in Claude MCP Server Ecosystem. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Claude MCP Server Ecosystem: ```json { "version": "1", "default": "deny", "tools": { "run_pipeline": { "limits": [ { "counter": "run_pipeline_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on Claude MCP Server Ecosystem (228) - `delete_enhanced_memory` — Destructive — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/delete-enhanced-memory.md - `delete_memory` — Destructive — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/delete-memory.md - `revoke_session` — Destructive — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/revoke-session.md - `undeploy_model` — Destructive — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/undeploy-model.md - `adaptive_cross_attention` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/adaptive-cross-attention.md - `adaptive_sparsity_tuning` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/adaptive-sparsity-tuning.md - `authenticate` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/authenticate.md - `benchmark_encoding_performance` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/benchmark-encoding-performance.md - `build_documentation_project` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/build-documentation-project.md - `compute_cross_attention` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/compute-cross-attention.md - `create_neural_network` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/create-neural-network.md - `create_security_scan` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/create-security-scan.md - `deploy_model` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/deploy-model.md - `deploy_plan` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/deploy-plan.md - `derive_key` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/derive-key.md - `execute_control_test` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-control-test.md - `execute_orchestration` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-orchestration.md - `execute_pipeline` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-pipeline.md - `execute_security_scan` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-security-scan.md - `execute_sparse_attention` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-sparse-attention.md - `execute_transformer_block` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-transformer-block.md - `execute_warehouse_query` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/execute-warehouse-query.md - `generate_attention_pattern` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/generate-attention-pattern.md - `generate_position_encodings` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/generate-position-encodings.md - `hyperparameter_search` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/hyperparameter-search.md - `initialize_cross_attention_session` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/initialize-cross-attention-session.md - `optimize_architecture` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/optimize-architecture.md - `optimize_attention_chunks` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/optimize-attention-chunks.md - `optimize_cross_attention_fusion` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/optimize-cross-attention-fusion.md - `optimize_gradient` — Execute — https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1/optimize-gradient.md - …and 198 more: https://policylayer.com/tools/coder-rl-claude-mcpserver-dev1.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=coder-rl-claude-mcpserver-dev1 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/coder-rl-claude-mcpserver-dev1