send_email_with_custom_config

send_email_with_custom_config

Server Email Sender MCP Server wyccywwyc/emailmcp
Category Write
Risk class Medium
Parameters 00 required

What send_email_with_custom_config does on Email Sender MCP Server

AI agents use send_email_with_custom_config to create or update resources in Email Sender MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email Sender MCP Server environment.

Why send_email_with_custom_config needs a policy

This tool sends emails, which modifies external state (recipient inboxes receive new messages). It does not read, execute arbitrary code, delete data, or move money. However, the severity is high rather than medium because unsupervised email sending could be abused for spam, phishing, impersonation, or business email compromise attacks, especially with custom SMTP configuration allowing flexibility in sender…

From the tool's definition Tool name is 'send_email_with_custom_config' and sibling tool 'send_email' is described as 'Enables sending emails through SMTP with support for multiple recipients, attachments, CC/BCC, and both plain text and HTML formats.' This tool creates outbound email…

Questions about send_email_with_custom_config

What does the send_email_with_custom_config tool do? +

send_email_with_custom_config. It is categorised as a Write tool in the Email Sender MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_email_with_custom_config? +

Register the Email Sender MCP Server MCP server in PolicyLayer and add a rule for send_email_with_custom_config: 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 Email Sender MCP Server. Nothing to install.

What risk level is send_email_with_custom_config? +

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

Can I rate-limit send_email_with_custom_config? +

Yes. Add a rate_limit block to the send_email_with_custom_config 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 send_email_with_custom_config completely? +

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

send_email_with_custom_config is provided by the Email Sender MCP Server MCP server (wyccywwyc/emailmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.