verify_otp_with_saved_mpin · Nubra MCP Server MCP

WHAT IT DOES

What verify_otp_with_saved_mpin does on Nubra MCP Server

AI agents invoke verify_otp_with_saved_mpin to trigger actions in Nubra MCP Server. 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 IT NEEDS A POLICY

Why verify_otp_with_saved_mpin needs a policy

This tool completes an authentication flow by verifying a one-time password and applying a saved MPIN to establish a session. It triggers an external authentication operation with stateful side effects (session creation/login), making it Execute rather than Read or Write. Misuse could allow unauthorized access to a trading account, but it requires possession of a valid OTP, moderately limiting blast radius.

From the tool's definition Verify OTP and then reuse the configured MPIN for the current environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verify_otp_with_saved_mpin Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_otp_with_saved_mpin": {
      "limits": [
        {
          "counter": "verify_otp_with_saved_mpin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 verify_otp_with_saved_mpin

What does the verify_otp_with_saved_mpin tool do? +

Recommended fast login completion when MPIN is already configured. Verify OTP and then reuse the configured MPIN for the current environment. It is categorised as a Execute tool in the Nubra MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on verify_otp_with_saved_mpin? +

Register the Nubra MCP Server MCP server in PolicyLayer and add a rule for verify_otp_with_saved_mpin: 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 verify_otp_with_saved_mpin? +

verify_otp_with_saved_mpin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit verify_otp_with_saved_mpin? +

Yes. Add a rate_limit block to the verify_otp_with_saved_mpin 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 verify_otp_with_saved_mpin completely? +

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

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