complete_connect_with_otp · Nubra MCP Server MCP

WHAT IT DOES

What complete_connect_with_otp does on Nubra MCP Server

AI agents use complete_connect_with_otp to create or update resources in Nubra MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nubra MCP Server environment.

WHY IT NEEDS A POLICY

Why complete_connect_with_otp needs a policy

This tool completes an authentication flow by verifying credentials (OTP and MPIN) and establishing a session. It creates/modifies an authenticated session state, making it a Write operation. Misuse could allow an attacker to authenticate as the user and gain access to trading capabilities, but the tool itself is completing auth rather than directly moving money or destroying data.

From the tool's definition Verify OTP, reuse the MPIN that was provided earlier, and confirm the logged-in environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_connect_with_otp Rate-limited

complete_connect_with_otp 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_connect_with_otp": {
      "limits": [
        {
          "counter": "complete_connect_with_otp_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nubra MCP Server, so you can run agents against it safely.

FAQ

Questions about complete_connect_with_otp

What does the complete_connect_with_otp tool do? +

Second step of the guided connect flow. Verify OTP, reuse the MPIN that was provided earlier, and confirm the logged-in environment. It is categorised as a Write tool in the Nubra MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_connect_with_otp? +

Register the Nubra MCP Server MCP server in PolicyLayer and add a rule for complete_connect_with_otp: 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 Nubra MCP Server. Nothing to install.

What risk level is complete_connect_with_otp? +

complete_connect_with_otp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit complete_connect_with_otp? +

Yes. Add a rate_limit block to the complete_connect_with_otp 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.

How do I block complete_connect_with_otp completely? +

Set action: deny in the PolicyLayer policy for complete_connect_with_otp. 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.

What MCP server provides complete_connect_with_otp? +

complete_connect_with_otp is provided by the Nubra MCP Server MCP server (socials-zanskar/nubra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.