Back to Feed
Agents / Safety & Alignment

Enforcing Organizational Policies in LLM Agents

Original: PolicyGuide: From Guarding One Action to Guiding the Whole Workflow for Policy-Compliant LLM Agents

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 2 concepts

Key Takeaways

  • Translates business policies into formal workflow graphs defining actors, actions, and satisfaction conditions.
  • Utilizes an external runtime verifier to maintain state across conversational turns.
  • Improves compliance in complex domains, achieving a mean Pass 4 rate of 0.61 in Telecom, up from 0.19.
  • Supports multiple frontier models including GPT 5.4, Claude Sonnet 4.6, and Gemini 2.5 Pro.

Summary & Methodology Analysis

PolicyGuide addresses the gap where LLM agents, typically running general-purpose reasoning-and-acting loops, fail to adhere to mandatory business procedures or execute unauthorized actions. The methodology compiles organizational policies into a formal workflow graph. This graph tracks state through nodes that specify required actors, actions, and logical satisfaction conditions. By decoupling policy enforcement from the agent's core reasoning, the system can persist the workflow state across multiple user turns using an external runtime verifier. This verifier gates mutating tool calls, ensuring that an agent can only perform an action if all necessary upstream prerequisites are verified against the conversation history and previous tool outputs. At each turn, the system reconciles open requests and traverses the graph to confirm node satisfaction, stopping the agent to provide remediation if a step is skipped or improperly executed. The approach is validated on models such as GPT 5.4, Claude Sonnet 4.6, and Gemini 2.5 Pro, showing significant performance gains in highly structured domains like Telecom. The system was also tested for adversarial robustness using the CRAFT red-teaming framework. While effective, the paper notes that PolicyGuide is a probabilistic aid rather than a formal guarantee. The implementation is fail-open, meaning it does not provide an unconditional compliance guarantee, and deployments for high-stakes actions should incorporate additional deterministic monitors.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the primary purpose of PolicyGuide?

It serves as a system to ensure LLM agents comply with organizational policies, preventing them from performing forbidden actions or skipping mandatory steps.

Q2. Does this tool work with any LLM?

The paper demonstrates that the workflows transfer to GPT 5.4, Claude Sonnet 4.6, and Gemini 2.5 Pro.

Q3. Is this a complete security solution?

No, it is a probabilistic aid and should not be used as the sole control for high-stakes actions.

Q4. How does the system handle state?

It uses an external runtime verifier to persist the workflow graph state across conversational turns.

Q5. What happens if a policy check fails?

The system stops at the first unsatisfied node and returns targeted remediation to the agent.

Q6. Are there specific requirements for high-stakes deployments?

Yes, because the verifier is fail-open, deployments requiring hard guarantees must include an additional deterministic monitor for the formally expressible policy subset.

Q7. How is the performance measured?

The paper uses a mean Pass 4 metric, observing an improvement from 0.19 to 0.61 in the Telecom domain.

Q8. How was the system tested against adversarial attacks?

The paper evaluated adversarial robustness using the CRAFT red-teaming framework.

Q9. Does the system guarantee 100% compliance?

No, the paper specifies that the verifier exceptions are fail-open, meaning it does not provide an unconditional guarantee of compliance.

Flag an issue

What is wrong with this summary?

What is wrong?