rolling-stock
Fetch rolling stock (vehicle) information
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/rolling-stock.md
What rolling-stock does on Meta Data Mcp
AI agents call rolling-stock 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.
Why rolling-stock is rated Low
The tool retrieves vehicle/rolling stock data from what is presumed to be a public open data API. No creation, modification, deletion, execution, or financial transaction occurs. The scope is read-only access to structured data, posing minimal risk if misused by an agent. Confidence is high as the terminology and server context clearly indicate a data retrieval pattern.
From the tool's definition Tool name 'rolling-stock' with description 'Fetch rolling stock (vehicle) information' indicates a retrieval operation. The verb 'Fetch' denotes querying data without modification.
Attacks that exploit this kind of access
The rule that runs rolling-stock 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 rolling-stock, this is the rule to start with:
rolling-stock is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every rolling-stock call is checked against it from then on.
Questions about rolling-stock
Fetch rolling stock (vehicle) information. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for rolling-stock: 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.
rolling-stock 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 rolling-stock 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 rolling-stock. 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.
rolling-stock 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.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue