AI agents call get_station_schedule to retrieve information from SNCF API 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 train schedule information from the SNCF API without modifying data or triggering operations. Despite empty description, the name and server context clearly indicate this is a data retrieval operation with minimal risk. A misused agent could only retrieve excessive schedule data, posing low impact.
From the tool's definition Tool name 'get_station_schedule' indicates retrieval of schedule/timetable data. Context shows sibling tools (check_disruptions, get_station_details, plan_journey_by_city_names) are all Read operations for railway information queries.
Documented attack patterns abuse exactly the kind of access get_station_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SNCF API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_station_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"get_station_schedule": {}
}
}get_station_schedule is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_station_schedule. It is categorised as a Read tool in the SNCF API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SNCF API MCP Server MCP server in PolicyLayer and add a rule for get_station_schedule: 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 SNCF API MCP Server. Nothing to install.
get_station_schedule 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 get_station_schedule 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 get_station_schedule. 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.
get_station_schedule is provided by the SNCF API MCP Server MCP server (kryzo/mcp-sncf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SNCF API 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.
4 SNCF API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.