release_sim_lock · SimRelay MCP Server MCP: Risk & Policy

WHAT IT DOES

What release_sim_lock does on SimRelay MCP Server

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

WHY IT NEEDS A POLICY

Why release_sim_lock needs a policy

This tool modifies SIM lock state, which is a reversible state change (Write category). It is idempotent and safe to call even if lock already expired, reducing risk. However, misuse could unlock SIMs inappropriately, disrupting legitimate locking mechanisms for SIM management.

From the tool's definition Tool name 'release_sim_lock' and description 'Release a previously acquired lock on a SIM' indicate modification of SIM state. The server enables management of SimRelay SIMs including 'lock, release' operations, showing this modifies SIM lock status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

release_sim_lock Rate-limited

release_sim_lock 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": {
    "release_sim_lock": {
      "limits": [
        {
          "counter": "release_sim_lock_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 SimRelay MCP Server, so you can run agents against it safely.

FAQ

Questions about release_sim_lock

What does the release_sim_lock tool do? +

Release a previously acquired lock on a SIM. Idempotent — safe to call even if the lock has already expired or never existed. It is categorised as a Write tool in the SimRelay 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 release_sim_lock? +

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

What risk level is release_sim_lock? +

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

Can I rate-limit release_sim_lock? +

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

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

release_sim_lock is provided by the SimRelay MCP Server MCP server (simrelay/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.