List all services in a Railway project.
AI agents call railway_list_services to retrieve information from Railway MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays existing services without creating, modifying, deleting, or executing any changes to Railway infrastructure. This is a pure read operation with no side effects, making it low severity even in a cloud management context where an agent could inventory services but cannot act upon them without other tools.
From the tool's definition Tool name 'railway_list_services' with description 'List all services in a Railway project' indicates a query/retrieval operation with no modification or execution of infrastructure.
Attacks that exploit this kind of access
List all services in a Railway project. It is categorised as a Read tool in the Railway MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Railway MCP Server MCP server in PolicyLayer and add a rule for railway_list_services: 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.
railway_list_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the railway_list_services 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 railway_list_services. 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.
railway_list_services 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.
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 →