# find_licensed_supplier

Licensed parties for a presentation in a jurisdiction (tenant as a parameter). Takes the decision_id of an allow or require_rx decision from gate_transaction.

Agent View of the PolicyLayer registry record for `find_licensed_supplier`. HTML page: https://policylayer.com/tools/a2a-peptides/find-licensed-supplier

## Facts

- Tool: `find_licensed_supplier`
- Server: A2A-Peptides (`https://mcp.a2a-peptides.ai/mcp`) — https://policylayer.com/tools/a2a-peptides.md
- Homepage: https://github.com/A2A-Peptides/A2A-Peptides
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 4 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tenant` | object | no |  |
| `decision_id` | string | yes |  |
| `jurisdiction` | string | yes |  |
| `presentation_id` | string | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_licensed_supplier",
    "arguments": {
      "decision_id": "<decision_id>",
      "jurisdiction": "<jurisdiction>",
      "presentation_id": "<presentation_id>"
    }
  }
}
```

## Why find_licensed_supplier is rated Low

Even though find_licensed_supplier only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call find_licensed_supplier to retrieve information from A2A-Peptides without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches A2A-Peptides:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_licensed_supplier": {}
  }
}
```

## Other tools on A2A-Peptides (19)

- `a2a_handoff` — Read — https://policylayer.com/tools/a2a-peptides/a2a-handoff.md
- `compare_presentations` — Read — https://policylayer.com/tools/a2a-peptides/compare-presentations.md
- `get_availability` — Read — https://policylayer.com/tools/a2a-peptides/get-availability.md
- `get_compounding_eligibility` — Read — https://policylayer.com/tools/a2a-peptides/get-compounding-eligibility.md
- `get_enforcement_watch` — Read — https://policylayer.com/tools/a2a-peptides/get-enforcement-watch.md
- `get_item` — Read — https://policylayer.com/tools/a2a-peptides/get-item.md
- `get_label_and_indication` — Read — https://policylayer.com/tools/a2a-peptides/get-label-and-indication.md
- `get_lot_coa` — Read — https://policylayer.com/tools/a2a-peptides/get-lot-coa.md
- `get_pathway_status` — Read — https://policylayer.com/tools/a2a-peptides/get-pathway-status.md
- `get_price` — Read — https://policylayer.com/tools/a2a-peptides/get-price.md
- `get_safety_label` — Read — https://policylayer.com/tools/a2a-peptides/get-safety-label.md
- `get_substance_record` — Read — https://policylayer.com/tools/a2a-peptides/get-substance-record.md
- `search_cleared_items` — Read — https://policylayer.com/tools/a2a-peptides/search-cleared-items.md
- `verify_serialization` — Read — https://policylayer.com/tools/a2a-peptides/verify-serialization.md
- `create_order_intent` — Write — https://policylayer.com/tools/a2a-peptides/create-order-intent.md
- `gate_transaction` — Write — https://policylayer.com/tools/a2a-peptides/gate-transaction.md
- `log_audit` — Write — https://policylayer.com/tools/a2a-peptides/log-audit.md
- `resolve_actor` — Write — https://policylayer.com/tools/a2a-peptides/resolve-actor.md
- `resolve_jurisdiction` — Write — https://policylayer.com/tools/a2a-peptides/resolve-jurisdiction.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a2a-peptides · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a2a-peptides
