Authenticate with Perkakasku using email and password. Returns a session token and merges anonymous cart into the account.
AI agents use login to create or update resources in Perkakasku — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Perkakasku environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | User email address |
password | string | Yes | User account password |
Parameters from the server's own tool schema.
Login creates a new authenticated session (a stateful write operation) and also merges/modifies cart state by combining anonymous cart data into the account. While authentication is often treated as a read-like action, the side effect of merging cart data constitutes a reversible write.
From the tool's definition 'Authenticate with Perkakasku using email and password. Returns a session token and merges anonymous cart into the account.'
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
Authenticate with Perkakasku using email and password. Returns a session token and merges anonymous cart into the account. It is categorised as a Write tool in the Perkakasku MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
login accepts 2 parameters: email, password. Required: email, password. The full parameter table on this page comes from the server's own tool schema.
Register the Perkakasku MCP server in PolicyLayer and add a rule for 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 Perkakasku. Nothing to install.
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 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 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.
login is provided by the Perkakasku MCP server (perkakasku-mcp-server). 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 →