Get airline check-in URLs
AI agents call checkin_links to retrieve information from Travel Amadeus 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 check-in URLs from airline data, which is a read-only operation with no side effects. It does not create, modify, delete, execute code, or commit financial transactions. The worst-case misuse would be providing incorrect or fraudulent URLs, which is a low-severity data integrity concern rather than a system-level risk.
From the tool's definition Tool name 'checkin_links' and description 'Get airline check-in URLs' indicate retrieval of URLs without modifying data or triggering actions. The action is purely informational—fetching and returning check-in links.
Attacks that exploit this kind of access
Get airline check-in URLs. It is categorised as a Read tool in the Travel Amadeus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Amadeus MCP Server MCP server in PolicyLayer and add a rule for checkin_links: 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 Travel Amadeus MCP Server. Nothing to install.
checkin_links 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 checkin_links 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 checkin_links. 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.
checkin_links is provided by the Travel Amadeus MCP Server MCP server (prathush21/travel-amadeus-mcp). 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 →