Create an MX record (mail exchange) for a domain
AI agents use create_mx_record to create or update resources in Spaceship MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spaceship MCP Server environment.
This tool creates DNS MX records, which configure mail routing for a domain. While the operation is reversible (records can be updated or deleted), modifying MX records can disrupt email delivery if misconfigured, making it a high-severity write operation with significant business impact.
From the tool's definition Tool name is 'create_mx_record' with description 'Create an MX record (mail exchange) for a domain'. The verb 'create' indicates a write operation that modifies DNS records, which are reversible via update/delete operations.
Documented attack patterns abuse exactly the kind of access create_mx_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Spaceship MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_mx_record:
{
"version": "1",
"default": "deny",
"tools": {
"create_mx_record": {
"limits": [
{
"counter": "create_mx_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_mx_record stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create an MX record (mail exchange) for a domain. It is categorised as a Write tool in the Spaceship MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spaceship MCP Server MCP server in PolicyLayer and add a rule for create_mx_record: 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 Spaceship MCP Server. Nothing to install.
create_mx_record 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_mx_record 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_mx_record. 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_mx_record is provided by the Spaceship MCP Server MCP server (mattcollins/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Spaceship MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Spaceship MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.