Close the Fidelity browser session and save cookies for faster re-login next time.
AI agents invoke fidelity_logout to trigger actions in Claude Fidelity. 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.
This tool terminates an active browser session (a side-effectful browser action) and saves cookie data to disk. It doesn't move money or delete data irreversibly, but it does execute browser automation actions with external state effects (ending a session, persisting cookies).
From the tool's definition 'Close the Fidelity browser session and save cookies for faster re-login next time'
Attacks that exploit this kind of access
Close the Fidelity browser session and save cookies for faster re-login next time. It is categorised as a Execute tool in the Claude Fidelity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Fidelity MCP server in PolicyLayer and add a rule for fidelity_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 Claude Fidelity. Nothing to install.
fidelity_logout is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fidelity_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.
Set action: deny in the PolicyLayer policy for fidelity_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.
fidelity_logout is provided by the Claude Fidelity MCP server (tylerflar/claude-fidelity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →