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.
This record as markdown: /tools/com-gatecoreai-marketplace/procure.md
What procure does on GateCore Marketplace
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
scopes | object | — | |
listing_id | string | Yes | |
max_price_cents | object | — | |
requester_trust | number | Yes | |
requester_agent_id | string | Yes |
Parameters from the server's own tool schema.
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.
Attacks that exploit this kind of access
The rule that runs procure safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GateCore Marketplace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For procure, this is the rule to start with:
procure is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GateCore Marketplace, apply this rule, and every procure call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the GateCore Marketplace MCP Server, which means it retrieves data without modifying state.
procure accepts 5 parameters: scopes, listing_id, max_price_cents, requester_trust, requester_agent_id. Required: listing_id, requester_trust, requester_agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the GateCore Marketplace MCP server in PolicyLayer and add a rule for procure: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches GateCore Marketplace. Nothing to install.
procure is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the procure rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for procure. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
procure is provided by the GateCore Marketplace MCP server (https://mcp.gatecoreai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GateCore Marketplace, and thousands of servers like it.
This server
Across the catalogue