Envia um e-mail transacional e aguarda o status de entrega final (polling automático por até ~10s). Executa pre-flight automático antes do envio: valida definition, asset, content blocks, campos isRequired da DE, atributos AMPscript, RaiseError guards e normaliza nomes contra a DE. Se houver erro...
Part of the Ljit Mcp Sfmc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use txn_send_email_and_check to create or modify resources in Ljit Mcp Sfmc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call txn_send_email_and_check repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ljit Mcp Sfmc.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
txn_send_email_and_check:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Ljit Mcp Sfmc policy for all 30 tools.
Agents calling write-class tools like txn_send_email_and_check have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Envia um e-mail transacional e aguarda o status de entrega final (polling automático por até ~10s). Executa pre-flight automático antes do envio: valida definition, asset, content blocks, campos isRequired da DE, atributos AMPscript, RaiseError guards e normaliza nomes contra a DE. Se houver erros bloqueantes, retorna sent=false com o relatório de pre-flight sem enviar. Retorna preflight + resultado do envio + status consolidado em uma única chamada. O messageKey é opcional e será gerado automaticamente se não informado.. It is categorised as a Write tool in the Ljit Mcp Sfmc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for txn_send_email_and_check. 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_send_email_and_check is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the txn_send_email_and_check 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_send_email_and_check. 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_send_email_and_check 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