Create a new sending domain (Sidemail API)
AI agents use create-domain to create or update resources in Sidemail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sidemail MCP Server environment.
This tool creates a new domain configuration within Sidemail, a transactional email service. Domain creation is a reversible Write operation (the domain can be deleted via the sibling 'delete-domain' tool). However, severity is elevated to 'medium' rather than 'low' because misconfiguration or unauthorized domain creation could affect email deliverability, enable spoofing if not properly validated, or incur costs.
From the tool's definition Tool name 'create-domain' and description 'Create a new sending domain' explicitly indicate creation of a new resource.
Attacks that exploit this kind of access
Create a new sending domain (Sidemail API). It is categorised as a Write tool in the Sidemail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sidemail MCP Server MCP server in PolicyLayer and add a rule for create-domain: 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 Sidemail MCP Server. Nothing to install.
create-domain 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 create-domain 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.
Set action: deny in the PolicyLayer policy for create-domain. 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.
create-domain is provided by the Sidemail MCP Server MCP server (sidemail/sidemail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →