Log in to your Rivian account. Rivian will send a verification code to your phone or email — use rivian_submit_otp to complete sign-in.
AI agents use rivian_login to create or update resources in Rivian MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rivian MCP environment.
Logging in creates an authenticated session (a state change on the server) and triggers an external action (sending an OTP via SMS or email). This is more than a pure read — it initiates a multi-step authentication flow with side effects. It does not destroy data or move money, so Write is the most appropriate category.
From the tool's definition 'Log in to your Rivian account' — initiates an authentication session, which creates server-side session state and triggers an OTP to be sent to the user's phone or email.
Attacks that exploit this kind of access
Log in to your Rivian account. Rivian will send a verification code to your phone or email — use rivian_submit_otp to complete sign-in. It is categorised as a Write tool in the Rivian MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rivian MCP server in PolicyLayer and add a rule for rivian_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 Rivian MCP. Nothing to install.
rivian_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 rivian_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 rivian_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.
rivian_login is provided by the Rivian MCP server (patrickheneise/rivian-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 →