Skip to content

Agent authentication file access

A tool call refers to an authentication-related path for an AI agent platform.

A compromised session could collect credentials used by other developer tools and extend its access to additional accounts.

While editing an application, an agent opens a different coding assistant authentication file without an account-migration task.

This is a fictional example, not an event from a customer.

The rule matches selected authentication-related paths for Cursor, Windsurf, Gemini, Codex, Copilot, and Aider. It does not compare the active platform with the platform that owns the file.

Rule IDEvent categoryTierBase severity
RULE_CROSS_AGENT_AUTH_ACCESScross_agentCommunityHIGH

Base severity is the rule default. A finding involving content saved for later execution may have a lower severity. Your loaded rule version and event details determine the finding you see.

Check which application owns the file and why access was requested. Avoid copying account credentials between tools; use each provider supported sign-in flow.

An agent reading its own authentication file or performing an approved account migration may trigger the rule. The cross_agent event category alone does not prove cross-platform access.

Unlisted platforms, renamed authentication files, unsupported path fields, or credentials retrieved without a visible file reference may be missed.

Matching is based on path names, not credential validity, file contents, or the identity of the active agent.

A finding describes a pattern in captured activity. Review the original call, its result, and the task context before concluding that harm occurred. Absence of a finding does not establish that an operation is safe.

Browse this category. Find a rule by ID.