Log the user in via a third-party provider token (e.g. Google) already obtained by the client.
AI agents use SOCIAL_AUTH_LOGIN to create or update resources in Travel Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Travel Agent MCP Server environment.
This tool establishes an authenticated session for a user using a third-party OAuth token. It creates or modifies session/authentication state on the server — a reversible Write action (sessions can be terminated).
From the tool's definition Log the user in via a third-party provider token (e.g. Google) already obtained by the client.
Attacks that exploit this kind of access
Log the user in via a third-party provider token (e.g. Google) already obtained by the client. It is categorised as a Write tool in the Travel Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for SOCIAL_AUTH_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 Travel Agent MCP Server. Nothing to install.
SOCIAL_AUTH_LOGIN is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the SOCIAL_AUTH_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 SOCIAL_AUTH_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.
SOCIAL_AUTH_LOGIN is provided by the Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). 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 →