Medium Risk

txn_send_test_email

Fluxo completo e confiável para envio de e-mail de teste. SEMPRE use esta tool quando o usuário pedir um envio de teste — ela garante transparência total do resultado. Executa: (1) pre-flight completo (definition, asset, campos isRequired da DE, AMPscript, RaiseError guards, normalização de atrib...

Part of the Ljit Mcp Sfmc server.

txn_send_test_email can modify Ljit Mcp Sfmc data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LJIT MCP SFMC →

Free to start. No card required.

AI agents use txn_send_test_email 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_test_email repeatedly, creating or modifying resources faster than any human could review. PolicyLayer'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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "txn_send_test_email": {
      "limits": [
        {
          "counter": "txn_send_test_email_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Ljit Mcp Sfmc policy for all 40 tools.

Get this rule live on your own Ljit Mcp Sfmc server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LJIT MCP SFMC →

View all 40 tools →

These attack patterns abuse exactly the kind of access txn_send_test_email gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so txn_send_test_email only ever does what you allow.

SECURE LJIT MCP SFMC →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the txn_send_test_email tool do? +

Fluxo completo e confiável para envio de e-mail de teste. SEMPRE use esta tool quando o usuário pedir um envio de teste — ela garante transparência total do resultado. Executa: (1) pre-flight completo (definition, asset, campos isRequired da DE, AMPscript, RaiseError guards, normalização de atributos); (2) se o pre-flight falhar, retorna a lista exata de campos obrigatórios ausentes e NÃO envia; (3) se passar, envia com atributos normalizados; (4) aguarda status real do SFMC com polling automático (até ~10s); (5) retorna success=true APENAS se o SFMC confirmar a entrega (EmailSent). Campos "attributes" devem conter todos os campos obrigatórios da DE e do template AMPscript. 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.

How do I enforce a policy on txn_send_test_email? +

Register the Ljit Mcp Sfmc MCP server in PolicyLayer and add a rule for txn_send_test_email: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ljit Mcp Sfmc. Nothing to install.

What risk level is txn_send_test_email? +

txn_send_test_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit txn_send_test_email? +

Yes. Add a rate_limit block to the txn_send_test_email rule in your PolicyLayer 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.

How do I block txn_send_test_email completely? +

Set action: deny in the PolicyLayer policy for txn_send_test_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.

What MCP server provides txn_send_test_email? +

txn_send_test_email is provided by the Ljit Mcp Sfmc MCP server (ljit-mcp-sfmc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ljit Mcp Sfmc tool call.

Deterministic rules across all 40 Ljit Mcp Sfmc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.