Get MT Travel service information and available endpoints.
AI agents call mt_travel_info to retrieve information from MolTrust MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static or semi-static information about a travel service and its endpoints. The verb 'Get' combined with 'information' and 'endpoints' indicates a read-only query with no side effects. No data is modified, deleted, or executed. Given the server context (trust infrastructure, DIDs, credentials), this appears to be a metadata/documentation endpoint.
From the tool's definition Tool description states 'Get MT Travel service information and available endpoints' — a purely informational query operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get MT Travel service information and available endpoints. It is categorised as a Read tool in the MolTrust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MolTrust MCP Server MCP server in PolicyLayer and add a rule for mt_travel_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 MolTrust MCP Server. Nothing to install.
mt_travel_info 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 mt_travel_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.
Set action: deny in the PolicyLayer policy for mt_travel_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.
mt_travel_info is provided by the MolTrust MCP Server MCP server (pypi:moltrust-mcp-server). 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 →