Clear stored Chase session cookies. Use this to log out or reset authentication state.
AI agents call chase_auth_clear to permanently remove resources in Chase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing stored session cookies is an irreversible action that destroys authentication state. The session cookies cannot be recovered once cleared — the user would need to re-authenticate. While not financially destructive, it disrupts access to the Chase account interface and cannot be undone without a new login flow, placing it in the Destructive category over Write.
From the tool's definition Clear stored Chase session cookies. Use this to log out or reset authentication state.
Attacks that exploit this kind of access
Clear stored Chase session cookies. Use this to log out or reset authentication state. It is categorised as a Destructive tool in the Chase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chase MCP Server MCP server in PolicyLayer and add a rule for chase_auth_clear: 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 Chase MCP Server. Nothing to install.
chase_auth_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the chase_auth_clear 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 chase_auth_clear. 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.
chase_auth_clear is provided by the Chase MCP Server MCP server (markswendsen-code/mcp-chase). 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 →