Skip to main content

Execution Rails

Execution rails control and validate tool calls, function execution, and action invocations. They ensure that external integrations, APIs, and custom actions are called safely with validated parameters and produce trusted results.

When Execution Rails Execute

Execution rails run before and after action/tool execution:
Execution rails are critical for agentic applications where LLMs make autonomous tool calls and API requests.

Key Concepts

Action Input Validation

Validate parameters before executing actions:

Action Output Validation

Verify results after execution:

Authorization Control

Enforce access control for tool calls:

Built-in Execution Rails

Action Parameter Validation

Validate action inputs using custom validators:
Usage in flows:

SQL Injection Prevention

Validate database queries:

File System Access Control

Validate file operations:

API Rate Limiting

Control API call frequency:
Usage:

Common Patterns

Pre-Execution Validation

Post-Execution Sanitization

Retry with Validation

Sandboxed Execution

Real-World Examples

E-commerce Transaction Validation

Database Query Execution

External API Integration

Best Practices

  1. Validate all external inputs - Never trust user-provided parameters
  2. Implement defense in depth - Layer multiple validation checks
  3. Use least privilege - Only grant necessary permissions for actions
  4. Set timeouts - Prevent long-running or hanging operations
  5. Sanitize outputs - Remove sensitive data from action results
  6. Log all executions - Track action calls for security auditing
  7. Implement rate limiting - Prevent abuse of expensive operations
  8. Use sandboxing - Isolate untrusted code execution

Configuration

Register Custom Actions

Enable Action Logging

Security Considerations

Critical Security Practices:
  1. Never execute arbitrary code from user input without sandboxing
  2. Always validate file paths to prevent directory traversal
  3. Use parameterized queries to prevent SQL injection
  4. Implement proper authentication for privileged actions
  5. Rate limit expensive operations to prevent DoS
  6. Audit all action executions for security monitoring

Performance Impact

Troubleshooting

Action Validation Failures

Enable detailed logging:

Performance Issues

Cache validation results:

See Also