Elastic Cloud ACTION
Create Traffic Filter Ruleset
Create a new traffic filter ruleset in Elastic Cloud. The API requires a name, type, region, rules, and include-by-default flag. Note that
type and region cannot be changed after the ruleset is created. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Elastic Cloud account once, then configure and run Create Traffic Filter Ruleset from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "elastic_cloud-create-traffic-filter",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
elastic_cloud: { authProvisionId: "apn_xxxxxxx" },
name: "Name",
type: "Type",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "elastic_cloud-create-traffic-filter",
"configured_props": {
"elastic_cloud": { "authProvisionId": "apn_xxxxxxx" },
"name": "Name",
"type": "Type"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "elastic_cloud",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "elastic_cloud-create-traffic-filter",
arguments: {
name: "Name",
type: "Type",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
name Name | string | A human-readable name for the ruleset (e.g. allow-office-ips). Required |
type Type | string | The ruleset type. One of: ip, vpce, azure_private_endpoint, gcp_private_service_connect_endpoint, egress_firewall, remote_cluster. Required |
region Region | string | The cloud region (e.g. gcp-us-central1). Required |
description Description | string | Optional description of the ruleset (e.g. Office egress IPs). Optional |
includeByDefault Include By Default | boolean | Whether to apply this ruleset to all new deployments by default. Required |
rules Rules | string | JSON array of rule objects. Example: [{"source":"1.2.3.4/32"}] Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- elastic_cloud-create-traffic-filter
- Version
- 0.0.2
- App
- Elastic Cloud
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗