# Collection Access Decision Engine AI Agent Connect

> Collection Access Decision Engine manages the complex logic of granting or denying access to sensitive materials. It reconciles requester profiles against donor mandates, legal restrictions, and institutional policies to produce clear, actionable decisions like Approve, Decline, or Conditional Access.

## Overview
- **Category:** compliance
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_wInTGVl3o2fiBOvYnn1O4cRX40e506evEH5jPUq4/ai-agent-connect
- **Tags:** archives, library, compliance, policy, decision-engine

## Description

Managing access to sensitive archives or library collections involves juggling donor agreements, legal constraints, and internal policies. This MCP handles that heavy lifting by acting as a decision-support engine for your agent. Instead of manually cross-referencing a researcher's credentials against a stack of donor mandates, you let your AI client run the reconciliation. It checks if a requester meets institutional standards, verifies that no private donor agreements are violated, and confirms that the specific item's physical or legal constraints allow for the requested interaction. The engine then synthesizes these checks into a single outcome. You get a clear path forward, whether that is a full approval, a decline, or a request for more information from the user. This ensures your institution stays compliant with both legal requirements and private contracts without slowing down the research process.

## Tools

### analyze_request_eligibility_tool
This tool determines if a requester's profile matches your broad institutional access policies and any specific exception rules.

### check_donor_compliance_tool
Use this to ensure a request doesn't break any private agreements made with a collection's donor.

### evaluate_item_restrictions_tool
This tool checks the physical or legal constraints of a specific item to see if the requested interaction is allowed.

### synthesize_final_decision_tool
This tool aggregates all previous checks into one actionable decision with clear next steps.

## Prompt Examples

**Prompt:** 
```
Evaluate a request from a researcher to reproduce a digital image from the Smith Collection.
```

**Response:** 
```
Conditional Access: The request is approved provided the researcher signs the digital reproduction agreement and pays the standard processing fee.
```

**Prompt:** 
```
Check if a student is eligible to view the restricted historical archives.
```

**Response:** 
```
Approve: The student meets the age and membership requirements defined in the institutional access policy.
```

**Prompt:** 
```
Can a commercial entity access the donor-restricted manuscripts?
```

**Response:** 
```
Decline: The request violates the usage prohibitions established in the donor conditions for this collection.
```

## Capabilities

### Policy Reconciliation
Your agent compares requester profiles against institutional access rules.

### Donor Mandate Verification
The MCP checks requests against private agreements to prevent contract violations.

### Constraint Evaluation
It reviews specific item restrictions to ensure legal and physical compliance.

### Decision Synthesis
The engine combines multiple checks into a single Approve, Decline, or Conditional outcome.

### Compliance Automation
Your AI client handles the logic of matching users to restricted materials.

## Use Cases

### Researcher Access Requests
Evaluate if a researcher can use or reproduce specific archival items.

### Donor Agreement Enforcement
Verify that access requests do not violate specific conditions set by donors.

### Student Eligibility Checks
Confirm that students meet the necessary requirements to view restricted archives.

### Commercial Usage Review
Determine if commercial entities are permitted to interact with specific collections.

## Benefits

- Reduces manual cross-referencing of donor agreements.
- Standardizes decision outcomes across all access requests.
- Prevents accidental violations of private donor contracts.
- Provides clear next steps for conditional access approvals.

## How It Works

Connect your AI client to Vinkius to start running access evaluations immediately.

1. Connect your preferred MCP-compatible client to Vinkius.
2. Provide the requester profile and item details to your agent.
3. The agent runs the eligibility, donor, and restriction tools.
4. The engine synthesizes the results into a final decision.
5. You receive an actionable outcome like Approve or Decline.

## Frequently Asked Questions

**What kind of decisions can this MCP make?**
The engine produces four specific outcomes: Approve, Decline, Conditional Access, or Request-Information.

**How does it handle donor restrictions?**
It uses a specific tool to check every request against the private agreements and conditions established by the collection's donor.

**Can I use this with Claude or Cursor?**
Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, and Windsurf.

**Does it check legal constraints?**
Yes, it evaluates item restrictions to ensure the requested interaction complies with legal and physical constraints.

**What is the main purpose of this MCP?**
It is a decision-support engine designed to automate the reconciliation of requester identities against item restrictions and institutional policies.