ovapi-line-details

Fetch one Dutch transit line: metadata, ordered stops per journey

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/ovapi-line-details.md

WHAT IT DOES

What ovapi-line-details does on Meta Data Mcp

AI agents call ovapi-line-details 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 ovapi-line-details is rated Low

This tool retrieves static transit line information (metadata and stop sequences) from a public API without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk if misused by an AI agent—it can only return existing public transit data.

From the tool's definition Tool name 'ovapi-line-details' and description 'Fetch one Dutch transit line: metadata, ordered stops per journey' indicate data retrieval with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ovapi-line-details 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 ovapi-line-details, this is the rule to start with:

ovapi-line-details Allowed

ovapi-line-details 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": {
    "ovapi-line-details": {}
  }
}

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 ovapi-line-details call is checked against it from then on.

FAQ

Questions about ovapi-line-details

What does the ovapi-line-details tool do? +

Fetch one Dutch transit line: metadata, ordered stops per journey. 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 ovapi-line-details? +

Register the Meta Data MCP server in PolicyLayer and add a rule for ovapi-line-details: 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 ovapi-line-details? +

ovapi-line-details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ovapi-line-details? +

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

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

ovapi-line-details 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 397 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

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