rail-traffic-info

Fetch rail traffic information

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/rail-traffic-info.md

WHAT IT DOES

What rail-traffic-info does on Meta Data Mcp

AI agents call rail-traffic-info to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why rail-traffic-info is rated Low

This tool retrieves publicly available rail traffic data from an open government/transport data API. It performs a query operation without creating, modifying, deleting, or executing arbitrary code. No financial transactions or destructive actions are possible. The blast radius of misuse is minimal—an agent could only retrieve information already publicly available.

From the tool's definition Tool name 'rail-traffic-info' and description 'Fetch rail traffic information' indicate data retrieval with no modification or side effects. 'Fetch' is a read-only operation that queries open data APIs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rail-traffic-info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rail-traffic-info, this is the rule to start with:

rail-traffic-info Allowed

rail-traffic-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rail-traffic-info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every rail-traffic-info call is checked against it from then on.

FAQ

Questions about rail-traffic-info

What does the rail-traffic-info tool do? +

Fetch rail traffic information. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rail-traffic-info? +

Register the Meta Data MCP server in PolicyLayer and add a rule for rail-traffic-info: 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 Meta Data Mcp. Nothing to install.

What risk level is rail-traffic-info? +

rail-traffic-info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit rail-traffic-info? +

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

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

rail-traffic-info is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →