Create a guest session with limited permissions. No credentials required.
AI agents use dual_login_guest to create or update resources in DUAL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DUAL MCP Server environment.
This tool creates a new session (a write/state-creating action) on the DUAL Web3 OS. While it has limited permissions, it establishes an authenticated session that could be used to interact with blockchain infrastructure. The 'no credentials required' aspect raises the blast radius since it could be misused to generate many guest sessions or as a foothold for further actions.
From the tool's definition Create a guest session with limited permissions. No credentials required.
Attacks that exploit this kind of access
Create a guest session with limited permissions. No credentials required. It is categorised as a Write tool in the DUAL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_login_guest: 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 DUAL MCP Server. Nothing to install.
dual_login_guest 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 dual_login_guest 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 dual_login_guest. 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.
dual_login_guest is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-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 →