AI agents use create_email_test to create or update resources in Intodns — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intodns environment.
This tool creates a new session/resource (a test email address) on the IntoDNS.ai platform. It is a Write operation as it provisions a new entity with a time-limited validity. Misuse could involve creating many sessions to exhaust resources, but no financial, destructive, or code-execution risk is evident. Severity is medium due to potential session/resource abuse.
From the tool's definition Create a new IntoDNS.ai inbound email-test session. Returns a unique single-use test email address (valid 60 minutes)
Attacks that exploit this kind of access
Create a new IntoDNS.ai inbound email-test session. Returns a unique single-use test email address (valid 60 minutes) and a. It is categorised as a Write tool in the Intodns MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intodns MCP server in PolicyLayer and add a rule for create_email_test: 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 Intodns. Nothing to install.
create_email_test 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_email_test 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_email_test. 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_email_test is provided by the Intodns MCP server (rosconl/intodns-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 →