deactivate_agent

Deactivate an agent - it cannot make payments until reactivated. REQUIRES OPERATOR KEY.

SERVERLightning Wallet SOURCElightning-wallet-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/deactivate-agent.md

WHAT IT DOES

What deactivate_agent does on Lightning Wallet

AI agents call deactivate_agent to retrieve information from Lightning Wallet without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why deactivate_agent is rated Low

Even though deactivate_agent only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deactivate_agent safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Lightning Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deactivate_agent, this is the rule to start with:

deactivate_agent Allowed

deactivate_agent is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deactivate_agent": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every deactivate_agent call is checked against it from then on.

FAQ

Questions about deactivate_agent

What does the deactivate_agent tool do? +

Deactivate an agent - it cannot make payments until reactivated. REQUIRES OPERATOR KEY. It is categorised as a Read tool in the Lightning Wallet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on deactivate_agent? +

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

What risk level is deactivate_agent? +

deactivate_agent is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit deactivate_agent? +

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

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

deactivate_agent is provided by the Lightning Wallet MCP server (lightning-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Lightning Wallet, and thousands of servers like it.

This server

All 59 Lightning Wallet tools →

Across the catalogue

comfy_agent_compute on Comfy → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →