Topic starter
02/08/2026 11:46 am
TL;DR: Claude Code can read files, run shell commands, call APIs, and trigger workflows, but its protections are mostly model-level rather than runtime enforcement, according to Akto. That leaves engineering teams exposed to prompt injection, tool abuse, shadow deployments, and over-permissioned sessions that IAM and AppSec must govern more tightly.
Editorial analysis by NHI Mgmt Group, based on content published by Akto: “Claude Code Security: Risks, Limitations, and Best Practices for Agentic AI”.
Key questions
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Q: Why do agentic workflows increase the risk of indirect prompt injection?
A: Because they blend untrusted content and trusted instructions inside the same execution path.
Q: How do security teams know if runtime controls are actually working for AI workloads?
A: They should be able to reconstruct a complete sequence from prompt ingestion to process activity to identity use to data access.
Practitioner guidance
- Restrict high-risk permissions by default Treat dangerous-skip-permissions style execution as a privileged exception, not a normal workflow.
- Define tool allowlists before deployment Specify exactly which files, commands, APIs, and workflows the agent may use, then block everything else.
- Separate development and production access Keep agent runtime environments away from systems that can modify production infrastructure or expose sensitive data.
Bottom line: Claude Code security shows that model-level guardrails can reduce unsafe outputs without stopping unsafe actions in a live session.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:56 pm
Runtime control is the real governance boundary for agentic coding tools. A model that can reason about unsafe code is not the same as a system that can stop an unsafe action. The operational question is where enforcement happens when the agent can write, execute, and call tools in the same session. For practitioners, model evaluation is useful, but runtime authorisation is the control that changes risk.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should IAM and AppSec teams govern developer AI agents in production-adjacent environments?
A: They should treat the agent as a privileged non-human actor with narrowly scoped access, just like any other high-risk service identity. That means separating environments, limiting tool access, requiring approvals for exceptional actions, and tying every session to observable ownership. The goal is to govern delegated machine action, not just model output.
👉 Read our full editorial: Claude Code security exposes the limits of model-level guardrails