Inspeciona uma definição de e-mail transacional: busca a definition, o asset vinculado no Content Builder, resolve recursivamente CONTENTBLOCKBYID() e CONTENTBLOCKBYNAME() referenciados, extrai o schema de atributos necessários via análise AMPscript (incluindo guards RaiseError e paths dinâmicos)...
Part of the Ljit Mcp Sfmc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call txn_inspect_email_definition to retrieve information from Ljit Mcp Sfmc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though txn_inspect_email_definition only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
txn_inspect_email_definition:
rules:
- action: allowSee the full Ljit Mcp Sfmc policy for all 30 tools.
Agents calling read-class tools like txn_inspect_email_definition have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Inspeciona uma definição de e-mail transacional: busca a definition, o asset vinculado no Content Builder, resolve recursivamente CONTENTBLOCKBYID() e CONTENTBLOCKBYNAME() referenciados, extrai o schema de atributos necessários via análise AMPscript (incluindo guards RaiseError e paths dinâmicos), e retorna os campos da DE vinculada para validação. Use esta tool antes de enviar um e-mail de teste para entender o payload completo exigido.. It is categorised as a Read tool in the Ljit Mcp Sfmc MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for txn_inspect_email_definition. 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_inspect_email_definition is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the txn_inspect_email_definition 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_inspect_email_definition. 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_inspect_email_definition 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