railway_delete_variable

railway_delete_variable

Server Railway MCP Server travis-gilbert/railway-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What railway_delete_variable does on Railway MCP Server

AI agents call railway_delete_variable to permanently remove resources in Railway MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why railway_delete_variable needs a policy

The tool name unambiguously indicates deletion ('delete_variable'), which is an irreversible operation that cannot be undone. Even though the description is empty, the naming convention and context of a Railway infrastructure management server—where variables control deployment configuration, secrets, and environment settings—indicates this tool permanently removes configuration data.

From the tool's definition Tool name 'railway_delete_variable' directly indicates deletion of variables. Sibling tools on the same Railway management server include 'railway_delete_service', 'railway_bulk_set_variables', and 'railway_deploy', confirming this server manages critical…

Questions about railway_delete_variable

What does the railway_delete_variable tool do? +

railway_delete_variable. 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 railway_delete_variable? +

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

What risk level is railway_delete_variable? +

railway_delete_variable 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 railway_delete_variable? +

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

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

railway_delete_variable is provided by the Railway MCP Server MCP server (travis-gilbert/railway-mcp). 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.