splitifi_login
Resume a saved Splitifi session from a previous conversation. Pass your user_token from a previous splitifi_save_progress call.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-login.md
What splitifi_login does on Splitifi Intelligence MCP
AI agents use splitifi_login to create or update resources in Splitifi Intelligence MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Splitifi Intelligence MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_token | string | Yes | Your saved user token from splitifi_save_progress |
Parameters from the server's own tool schema.
Why splitifi_login is rated Medium
This tool authenticates/resumes a user session using a token, which involves creating or restoring session state on the server. It is not purely read-only (it establishes an authenticated session), but it does not execute code, delete data, or move money. Write is the most appropriate category as it creates/modifies session state.
From the tool's definition 'Resume a saved Splitifi session' and 'Pass your user_token from a previous splitifi_save_progress call'
Attacks that exploit this kind of access
The rule that runs splitifi_login safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Splitifi Intelligence MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For splitifi_login, this is the rule to start with:
splitifi_login stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Splitifi Intelligence MCP, apply this rule, and every splitifi_login call is checked against it from then on.
Questions about splitifi_login
Resume a saved Splitifi session from a previous conversation. Pass your user_token from a previous splitifi_save_progress call. It is categorised as a Write tool in the Splitifi Intelligence MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
splitifi_login accepts 1 parameter: user_token. Required: user_token. The full parameter table on this page comes from the server's own tool schema.
Register the Splitifi Intelligence MCP server in PolicyLayer and add a rule for splitifi_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 Splitifi Intelligence MCP. Nothing to install.
splitifi_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 splitifi_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 splitifi_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.
splitifi_login is provided by the Splitifi Intelligence MCP server (splitifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Splitifi Intelligence, and thousands of servers like it.
This server
Across the catalogue