High Risk →

maker_unlock_idle

Clear an idle-locked session without ending it. Admin-only.

How to control maker_unlock_idle ↓

What maker_unlock_idle does on Crow

AI agents invoke maker_unlock_idle to trigger actions in Crow. 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.

High Risk

Why maker_unlock_idle needs a policy

This tool triggers a session state change (unlocking an idle-locked session) on an external system. It is not a simple read, nor does it delete data, but it does execute an administrative action that changes system state. The 'Admin-only' designation indicates elevated privilege and potential for misuse if invoked without authorization.

From the tool's definition Clear an idle-locked session without ending it. Admin-only.

Risk signalsAdmin/system-level operation

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

How to control maker_unlock_idle

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "maker_unlock_idle": {
      "limits": [
        {
          "counter": "maker_unlock_idle_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about maker_unlock_idle

What does the maker_unlock_idle tool do? +

Clear an idle-locked session without ending it. Admin-only. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on maker_unlock_idle? +

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

What risk level is maker_unlock_idle? +

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

Can I rate-limit maker_unlock_idle? +

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

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

maker_unlock_idle is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

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

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.