Critical Risk →

domain_delete

[API] Delete a domain from a service ⚡️ Best for: ✓ Removing unused domains ✓ Cleaning up configurations ✓ Domain management ⚠️ Not for: × Temporary domain disabling × Port updates (use domain_update) → Prerequisites: domain_list → Alternatives: domain_update → Related: service_update

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

jason-tan-swe/railway-mcp Destructive Risk 4/5

AI agents may call domain_delete to permanently remove or destroy resources in Railway MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call domain_delete in a loop, permanently destroying resources in Railway MCP Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

jason-tan-swe-railway-mcp.yaml
tools:
  domain_delete:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Railway MCP Server policy for all 38 tools.

Tool Name domain_delete
Category Destructive
Risk Level Critical

View all 38 tools →

Agents calling destructive-class tools like domain_delete 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

domain_delete is one of the critical-risk operations in Railway MCP Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the domain_delete tool do? +

[API] Delete a domain from a service ⚡️ Best for: ✓ Removing unused domains ✓ Cleaning up configurations ✓ Domain management ⚠️ Not for: × Temporary domain disabling × Port updates (use domain_update) → Prerequisites: domain_list → Alternatives: domain_update → Related: service_update. It is categorised as a Destructive tool in the Railway MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on domain_delete? +

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

What risk level is domain_delete? +

domain_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit domain_delete? +

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

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

domain_delete is provided by the Railway MCP Server MCP server (jason-tan-swe/railway-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Railway MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.