lock_otp

THE RISK

High Risk

Why lock_otp needs a policy

This tool triggers an external operation (session lock) that changes system state by invalidating the current OTP session and blocking access to encrypted data. It is reversible (re-verification restores access), so it's not Destructive. It doesn't read, write, or move money — it executes a session management action with moderate blast radius since misuse could lock out legitimate access to personal data.

From the tool's definition Immediately lock the current OTP session and block access to encrypted personal data. Requires re-verification with verify_otp to access data again.

Documented attack patterns abuse exactly the kind of access lock_otp gives an agent:

POLICY

How to control lock_otp

PolicyLayer is an MCP gateway — it sits between your AI agents and Personal Context MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lock_otp:

policy.json

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

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

Create a free account and register Personal Context MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Personal Context MCP Server tools

Destructive delete_personal_info Delete specific personal information Execute disable_otp Disable OTP authentication and encryption for personal data. Write batch_save_personal_info Save multiple pieces of personal information in a single request. More efficient than maki Write update_personal_info Update existing personal information Read batch_get_personal_info Retrieve multiple categories of personal information in a single request. Retrieve persona Read list_available_personal_info List all available personal information within current permissions Read otp_status Check the current OTP configuration status and whether OTP verification is required. Read verify_otp Verify an OTP token to access encrypted personal data. Required before reading encrypted i

All 9 Personal Context MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Personal Context MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about lock_otp

What does the lock_otp tool do? +

Immediately lock the current OTP session and block access to encrypted personal data. Requires re-verification with verify_otp to access data again. It is categorised as a Execute tool in the Personal Context 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 lock_otp? +

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

What risk level is lock_otp? +

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

Can I rate-limit lock_otp? +

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

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

lock_otp is provided by the Personal Context MCP Server MCP server (matipojo/personal-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Personal Context MCP Server tool call.

Start from Personal Context MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →