High Risk →

logout_instance

Logout an instance (disconnects the WhatsApp session without deleting the instance)

How to control logout_instance ↓

What logout_instance does on Mcp Ap2

AI agents invoke logout_instance to trigger actions in Mcp Ap2. 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 logout_instance needs a policy

This tool triggers an external operation — disconnecting a WhatsApp session — without permanently deleting data. It is reversible (re-login is possible) but causes an operational side effect on an external service, placing it in Execute rather than Destructive or Write.

From the tool's definition 'Logout an instance (disconnects the WhatsApp session without deleting the instance)'

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

How to control logout_instance

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

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

logout_instance 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 Mcp Ap2 — 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 logout_instance

What does the logout_instance tool do? +

Logout an instance (disconnects the WhatsApp session without deleting the instance). It is categorised as a Execute tool in the Mcp Ap2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on logout_instance? +

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

What risk level is logout_instance? +

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

Can I rate-limit logout_instance? +

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

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

logout_instance is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 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.