Valida completamente um envio de e-mail transacional SEM enviá-lo (dry run). Verifica: status da definition (Active/Inactive), existência do asset no Content Builder, resolução recursiva de content blocks, atributos obrigatórios via análise AMPscript, guards RaiseError() que bloqueiam o envio, e ...
Part of the Ljit Mcp Sfmc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke txn_preflight_email to trigger processes or run actions in Ljit Mcp Sfmc. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
txn_preflight_email can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
txn_preflight_email:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Ljit Mcp Sfmc policy for all 30 tools.
Agents calling execute-class tools like txn_preflight_email have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
txn_preflight_email is one of the high-risk operations in Ljit Mcp Sfmc. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Valida completamente um envio de e-mail transacional SEM enviá-lo (dry run). Verifica: status da definition (Active/Inactive), existência do asset no Content Builder, resolução recursiva de content blocks, atributos obrigatórios via análise AMPscript, guards RaiseError() que bloqueiam o envio, e normalização de nomes de atributos contra o schema da DE. Retorna passed=true/false, errors[] (bloqueantes), warnings[] (não-bloqueantes), normalizedAttributes (atributos com nomes corrigidos prontos para uso) e requiredAttributes. Use antes de txn_send_email para garantir que o payload está correto. Quando generateMock=true, gera automaticamente um payload de teste sintético em mockPayload — usa row-sample da DE apenas para inferir tipos de campo, sem copiar valores reais.. It is categorised as a Execute tool in the Ljit Mcp Sfmc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for txn_preflight_email. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ljit Mcp Sfmc MCP server.
txn_preflight_email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the txn_preflight_email rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for txn_preflight_email. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
txn_preflight_email is provided by the Ljit Mcp Sfmc MCP server (ljit-mcp-sfmc). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept