stateset_customer_login
Authenticates a customer with email and password. Returns auth token for customer portal access.
This record as markdown: /tools/stateset-mcp-server/stateset-customer-login.md
What stateset_customer_login does on Stateset
AI agents invoke stateset_customer_login to trigger actions in Stateset. 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.
Why stateset_customer_login is rated High
Authentication operations involve executing an identity verification process and generating/returning access tokens. Misuse could lead to unauthorized access to customer accounts or session hijacking.
From the tool's definition Authenticates a customer with email and password. Returns auth token for customer portal access.
Attacks that exploit this kind of access
The rule that runs stateset_customer_login safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_customer_login, this is the rule to start with:
stateset_customer_login stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_customer_login call is checked against it from then on.
Questions about stateset_customer_login
Authenticates a customer with email and password. Returns auth token for customer portal access. It is categorised as a Execute tool in the Stateset MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_customer_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 Stateset. Nothing to install.
stateset_customer_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 stateset_customer_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 stateset_customer_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.
stateset_customer_login is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
Across the catalogue