Skip to main content
The Instances page shows a complete history of when governance rules were applied to block or modify agent behavior. This provides visibility into security enforcement.

Overview

Rule instances capture:
  • When a rule was triggered (timestamp)
  • Which rule was enforced (rule name and ID)
  • What happened (details of the blocked action)
  • Where it occurred (blocked URL, session link)
Instances are logged automatically whenever a governance rule blocks an action. Check this page regularly to monitor security enforcement.

Filter by Rule

The filter card at the top lets you show/hide instances by rule type:
1

Select rules to view

Click rule buttons to toggle visibility. Active rules are highlighted.
2

View instance counts

Each rule button shows the number of times it was triggered.
3

Use quick actions

  • Select All: Show instances for all rules
  • Clear All: Hide all instances

Available Rules

ContextFort currently tracks instances for these governance rules:

Disallow URLs with Query Parameters

Rule ID: disallow_query_params Prevents the agent from opening URLs with query parameters (e.g., ?param=value). Instance details show:
  • The URL that was blocked
  • The session where the block occurred
  • Timestamp of the attempt
This rule protects against data leakage through URL parameters and ensures clean URLs.

Disallow Printing Clickable URLs

Rule ID: disallow_clickable_urls Prevents the agent from printing clickable URLs in the Claude sidechat interface. Instance details show:
  • The URL that was blocked from being printed
  • The context where the print was attempted
  • Associated session

Instance Table

The main table displays all filtered instances, sorted by timestamp (most recent first).

Table Columns

ColumnDescription
TimestampDate and time when the rule was triggered
RuleName of the governance rule that was enforced
DetailsDescription of what was blocked (includes URL if applicable)
SessionLink to view the session where this occurred

Investigating an Instance

1

Identify the rule

Check the Rule column to see which governance policy was triggered.
2

Review the details

The Details column shows:
  • What action was blocked
  • The URL involved (if applicable)
  • Additional context
3

View the session

Click the link icon in the Session column to jump to the Visibility page and see screenshots from that session.
4

Correlate patterns

Look for repeated instances of the same rule on similar URLs or domains.

Session Linking

Instances with an associated session show a link icon. Clicking it navigates to:
/dashboard/visibility?session=<sessionId>
The session will auto-expand so you can review screenshots and events.
Not all instances have an associated session. Some rules may block actions before a session is created.

Empty States

No Rule Enforcement Instances

If you see this message:
  • No rules selected: Use the filter to select rules to view
  • No rules triggered: Governance rules haven’t blocked any actions yet
  • Rules not enabled: Check the Rules page to enable governance policies

Time Formatting

Timestamps are displayed in your local timezone:
  • Date: MMM DD, YYYY (e.g., “Jan 15, 2025”)
  • Time: HH:MM:SS in 24-hour format
  • Combined: “Jan 15, 2025 14:30:45”

Refreshing Data

Click the Refresh button to reload instances from Chrome storage:
  • Instances are loaded from chrome.storage.local (key: governanceInstances)
  • Data is sorted by timestamp (newest first)
  • Filter selections are preserved on refresh

Summary Statistics

At the bottom of the page, you’ll see:
Showing X instances across Y rules
This indicates:
  • X: Number of instances currently visible based on filters
  • Y: Number of rules currently selected in the filter

Use Cases

Security Auditing

Review instances to:
  • Verify that governance rules are working correctly
  • Identify patterns of blocked behavior
  • Audit agent compliance with security policies

Troubleshooting

If the agent can’t complete a task:
  • Check if a rule blocked a necessary action
  • Review the instance details to understand what was prevented
  • Temporarily disable the rule if needed (see Rules page)

Compliance Reporting

Export or review instances for:
  • Security compliance audits
  • Incident reports
  • Behavior analysis

Best Practices

1

Regular monitoring

Check the Instances page daily to stay aware of security enforcement.
2

Investigate spikes

If you see many instances suddenly, investigate whether:
  • A rule is too strict
  • The agent is attempting problematic behavior
  • There’s a configuration issue
3

Correlate with sessions

Always click through to sessions to see the full context of blocked actions.
4

Adjust rules as needed

Use instance data to inform whether rules should be modified or disabled.

Technical Details

The Instances page:
  • Loads from chrome.storage.local (key: governanceInstances)
  • Instances are created by background scripts when rules are triggered
  • Each instance has a unique ID and timestamp
  • Instances are never automatically deleted (manual cleanup required)

Next Steps

Configure Rules

Enable or disable governance rules

Review Sessions

See screenshots from sessions where rules were triggered

Build docs developers (and LLMs) love