Initiate Hilton Honors login flow. Returns a URL and instructions for the user to complete login manually. After logging in, use hilton_status to verify.
AI agents invoke hilton_login to trigger actions in Mcp Hilton. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external authentication flow via browser automation. It initiates a login session on Hilton's platform, which is an external operation with side effects (creating an authenticated session). It's not purely Read/Write to data, but executes a browser-driven auth flow.
From the tool's definition Initiate Hilton Honors login flow... browser automation
Attacks that exploit this kind of access
Initiate Hilton Honors login flow. Returns a URL and instructions for the user to complete login manually. After logging in, use hilton_status to verify. It is categorised as a Execute tool in the Mcp Hilton MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Hilton MCP server in PolicyLayer and add a rule for hilton_login: 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 Mcp Hilton. Nothing to install.
hilton_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hilton_login 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 hilton_login. 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.
hilton_login is provided by the Mcp Hilton MCP server (markswendsen-code/mcp-hilton). 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 →