Workbench tools
Configure external integrations for your workbench agents to call
Overview
Tools are reusable external integrations that workbench agents can call as part of a job. They are configured globally and then attached to individual workbenches, so the same Datadog connection or MCP server can be shared across multiple workbenches without re-entering credentials.
Navigate to Workbenches → Integrations to browse the available tool types, or Workbenches → Configured tools to manage the tools you have already set up.
Tool types
Plural native integrations
These capabilities are built directly into the workbench runtime and require no external credentials or tool setup. They are enabled per-workbench via the capability toggles in Step 1 of the creation wizard.
Capability | What the agent can access |
|---|---|
| Services | Plural-managed service deployments — health status, rollout history, configuration, and associated cluster |
| Stacks | IaC stack runs, Terraform state summaries, run logs, and failure details for Plural-managed stacks |
| Kubernetes | Full Kubernetes API access across your managed clusters — list and describe any resource (Deployments, Pods, Events, ConfigMaps, etc.) |
| Pod logs | Raw container stdout/stderr streamed directly from Kubernetes pods |
| Vulnerabilities | Trivy vulnerability findings auto-associated with Plural-managed services |
| Metrics | Query your configured Prometheus-compatible metrics backends via Plural's observability integration |
| Log aggregation | Search and aggregate logs from your configured backends (Loki, Elastic, etc.) via Plural's observability integration |
All native integrations respect your existing RBAC — enabling a capability here does not grant the agent access it would not otherwise have.