Coding Agent Security
Security guidance, enforcement and investigation for coding agents.
Heeler automatically supplies coding agents with applicable standards and sensitive-data requirements, checks supported actions, and evaluates the resulting changes against repository guardrails. Teams can investigate recorded sessions and assess agent files across repositories and enrolled workstations.
Automated security guidance and enforcement for coding agents.
Heeler automatically supplies applicable standards, repository guardrails and sensitive-data requirements, including PII. It checks supported changes and commands during development, blocks configured violations, and evaluates the resulting PR against the same repository guardrails.
Automatic inventory of agents and workstation configuration.
The Workstation Sensor reports the agents, skills, MCP servers and hooks on each machine.
Risk assessment for agent instructions, skills and MCP configuration.
Every agent file gets a safety score from 0 to 100 and an assessed intent.
Session risk findings with task context.
Review commands, tool output and the surrounding conversation. Heeler flags risky effects and considers whether the action matched the developer’s request.
Credential exposure and use across agent sessions.
Follow a credential from the prompt, a file read or tool output to its later use in commands, files, external requests, MCP calls or observed commits.
Cloud, database and external-service access by coding agents.
Inspect cloud, cluster, database and external-service activity. Review the target, available identity and environment context, and whether the observed operation reads or changes state.
Review the command and responseReview the named account and operationAccess capability not establishedAgent usage and estimated cost by model and repository.
Compare models, repositories, workstations and coding agents. Break down input, output and cached tokens, then open the sessions behind the totals.
Commit evidence linked to agent sessions.
Inspect the conversation, tool activity and commit evidence together. Heeler distinguishes commits created during a session from commits the agent only inspected, and links to the repository when it can resolve it.
How it deploys
Agent guidance, enforcement and investigation across the platform.
Agent instructions that conflict with security requirements.
Cross-check CLAUDE.md, .cursorrules and skills against model requirements. Instructions to skip authentication or call a production API directly can surface as findings tied to the affected requirement.
Agent instructions and threat modelsPurpose-built for the AI SDLC
