Critical Risk →

monarch_logout

Clear the stored Monarch Money session from the system keyring.

How to control monarch_logout ↓

AI agents call monarch_logout to permanently remove resources in Monarch — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly removes the stored session credentials from the system keyring. While it doesn't delete financial data, clearing the session is a destructive, non-reversible action that would revoke authenticated access and could not be undone without re-authenticating. Severity is medium as it disrupts access but doesn't directly destroy financial records.

From the tool's definition Clear the stored Monarch Money session from the system keyring

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "monarch_logout"
  ]
}

monarch_logout disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Monarch — 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the monarch_logout tool do? +

Clear the stored Monarch Money session from the system keyring. It is categorised as a Destructive tool in the Monarch MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on monarch_logout? +

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

What risk level is monarch_logout? +

monarch_logout is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit monarch_logout? +

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

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

monarch_logout is provided by the Monarch MCP server (robcerda/monarch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Monarch tool call.

Deterministic rules across all 50 Monarch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

50 Monarch tools catalogued and risk-classified — across an index of 42,500+ 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.