Medium Risk

truncus_send_email

Send a transactional email to a single recipient. Requires a verified sending domain.

Accepts raw HTML/template content (html); Single-target operation

Part of the Truncus MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use truncus_send_email to create or modify resources in Truncus. 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 truncus_send_email 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 Truncus.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

co-truncus-mcp-server.yaml
tools:
  truncus_send_email:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Truncus policy for all 6 tools.

Tool Name truncus_send_email
Category Write
MCP Server Truncus MCP Server
Risk Level Medium

Agents calling write-class tools like truncus_send_email have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the truncus_send_email tool do? +

Send a transactional email to a single recipient. Requires a verified sending domain.. It is categorised as a Write tool in the Truncus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on truncus_send_email? +

Add a rule in your Intercept YAML policy under the tools section for truncus_send_email. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Truncus MCP server.

What risk level is truncus_send_email? +

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

Can I rate-limit truncus_send_email? +

Yes. Add a rate_limit block to the truncus_send_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.

How do I block truncus_send_email completely? +

Set action: deny in the Intercept policy for truncus_send_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 truncus_send_email? +

truncus_send_email is provided by the Truncus MCP server (@truncus/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.