# procure

Request governed procurement for a listing. In public full mode, identity comes from the MCP access key, trust comes from GateCore's baseline, and the result is a PROCURE, REVIEW, or DENY decision with gateway delegation when eligible.

Agent View of the PolicyLayer registry record for `procure`. HTML page: https://policylayer.com/tools/com-gatecoreai-marketplace/procure

## Facts

- Tool: `procure`
- Server: GateCore Marketplace (`https://mcp.gatecoreai.com/mcp`) — https://policylayer.com/tools/com-gatecoreai-marketplace.md
- Homepage: https://github.com/GateCoreAI-com/gatecore-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 5 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `scopes` | object | no |  |
| `listing_id` | string | yes |  |
| `max_price_cents` | object | no |  |
| `requester_trust` | number | yes |  |
| `requester_agent_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": "procure",
    "arguments": {
      "listing_id": "<listing_id>",
      "requester_trust": 0,
      "requester_agent_id": "<requester_agent_id>"
    }
  }
}
```

## Why procure is rated Low

Even though procure 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 procure to retrieve information from GateCore Marketplace 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 GateCore Marketplace:

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

## Other tools on GateCore Marketplace (4)

- `discover_listings` — Read — https://policylayer.com/tools/com-gatecoreai-marketplace/discover-listings.md
- `get_listing` — Read — https://policylayer.com/tools/com-gatecoreai-marketplace/get-listing.md
- `list_procurements` — Read — https://policylayer.com/tools/com-gatecoreai-marketplace/list-procurements.md
- `submit_lead` — Write — https://policylayer.com/tools/com-gatecoreai-marketplace/submit-lead.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=com-gatecoreai-marketplace · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gatecoreai-marketplace