Topic starter
20/08/2026 5:39 pm
TL;DR: Agentic tool use shifts AWS Strands risk from content filtering to action control, according to ActiveFence. Runtime guardrails have to inspect inputs, tool calls and outputs before exposure if they are meant to stop confused-deputy failures and data leaks.
Editorial analysis by NHI Mgmt Group, based on content published by ActiveFence: “Secure AWS Strands Agents with Alice WonderFence”.
Key questions
Q: Why do authenticated users still create risk for agentic tool access?
A: Authentication only proves who entered the session, not whether the requested action fits the user's intent or entitlement.
Q: What signs show that agent guardrails are not working?
A: The warning signs are repeated secret detections, unexplained outbound communication, and developers disabling controls because they are too hard to use.
Q: What breaks when runtime guardrails are missing for agents?
A: The system loses the ability to stop unsafe inputs before they influence reasoning, block dangerous tool use before execution, and prevent sensitive outputs from reaching users.
Practitioner guidance
- Implement runtime policy checks for agent execution Validate user inputs, tool calls, and generated outputs before they can influence data access or external actions.
- Constrain delegated tool scope by task Limit each agent to the smallest set of tools, datasets, and parameters required for the current task so authenticated sessions cannot drift into broader data retrieval.
- Log policy decisions at each enforcement point Record what was inspected, what was allowed, what was blocked, and why so the security team can reconstruct agent behaviour after a sensitive interaction.
Bottom line: Agentic tool use expands the security problem from content moderation to action control, because a valid request can still produce an invalid outcome.
Glossary terms: Runtime Guardrail, Confused Deputy, Delegated Authority Model, Agentic Tool Authority
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
20/08/2026 6:24 pm
Runtime enforcement is now a governance requirement for agentic systems: agent risk is not contained at the model boundary, because the real control point is the moment an action is taken. When agents can call tools and fetch data, policy must be evaluated continuously, not assumed from the prompt or the session. Practitioners should treat the execution layer as the primary control plane.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: How should security teams compare runtime guardrails with prompt filtering?
A: Prompt filtering changes the text that enters or leaves the model, while runtime guardrails govern what the agent is allowed to do as it runs. The first reduces unsafe content, but the second controls action, privilege, and data flow. For agent security, those are complementary controls, not substitutes.
👉 Read our full editorial: Runtime guardrails for AWS Strands agents and tool misuse