elevenlabs-agents

Malicious tool definition detected

Edit $SIMULATION_FILE and run again." exit 0 fi echo "Running conversation simulation..." echo "Agent ID: $AGENT_ID" echo "Simulation file: $SIMULATION_FILE" # Run simulation curl -X POST "https://api.elevenlabs.io/v1/convai/agents/$AGENT_ID/simulate" \ -H "xi-api-key: $ELEVENLABS_API_KEY" \ -H "Content-Type: application/json" \ -d @"$SIMULATION_FILE" | jq .

Malicious tool definition detected

-f "agents.json" ]; then echo "Initializing project..." elevenlabs agents init fi # Create agent echo "Creating agent: $AGENT_NAME" elevenlabs agents add "$AGENT_NAME" --template "$TEMPLATE" # Push to platform echo "Deploying to environment: $ENV" elevenlabs agents push --env "$ENV" echo "✓ Agent created successfully!" echo "Edit configuration in: agent_configs/" echo "Test with: elevenlabs agents test \"$AGENT_NAME\""

Malicious tool definition detected

Please login:" elevenlabs auth login fi # Push tests to platform if [ -f "tests.json" ]; then echo "Deploying tests..." elevenlabs tests push fi # Run agent tests echo "Running tests for: $AGENT_NAME" elevenlabs agents test "$AGENT_NAME" echo "✓ Tests completed!"

Malicious tool definition detected

```json { "privacy": { "zero_retention": true } } ``` **Limitations**: - No conversation history - No analytics - No post-call webhooks - No MCP tool integrations --- ## PCI DSS (Payment Card Industry) ### Never: ❌ Store credit card numbers in conversation logs ❌ Send credit card data to LLM ❌ Log CVV or PIN numbers ### Always: ✅ Use PCI-compliant payment processors (Stripe, PayPal) ✅ Tokenize payment data ✅ Use DTMF keypad for card entry (telephony) ### Example: Secure Payment Collection ```jso

Malicious tool definition detected

# Dry run first to show changes echo "Preview of changes for $ENV:" if [ -n "$AGENT_NAME" ]; then elevenlabs agents push --env "$ENV" --agent "$AGENT_NAME" --dry-run else elevenlabs agents push --env "$ENV" --dry-run fi # Confirm deployment read -p "Deploy to $ENV?

Tool passed security scan