fetch
Get full detail on one published listing by its listing slug (not a contributor slug). Read-only, no authentication required (public endpoint, IP rate-limited). Returns title, description, short_description, product_story, included_components, use_cases, industry_focus, complexity_level, listing_...
This record as markdown: /tools/com-gallandigital-marketplace/fetch.md
What fetch does on Marketplace
AI agents call fetch to retrieve information from 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 |
|---|---|---|---|
slug | string | Yes | The listing's slug, as returned by search (the listing-level slug, not a contributor slug). |
Parameters from the server's own tool schema.
Why fetch is rated Low
This is a straightforward data retrieval operation with no side effects. It queries and returns public marketplace listing information without modifying, executing, or deleting any data. The read-only designation and public endpoint access confirm no mutation or execution risk.
From the tool's definition Tool description explicitly states 'Read-only, no authentication required (public endpoint, IP rate-limited)'. Function retrieves full details of published marketplace listings by slug.
Attacks that exploit this kind of access
The rule that runs fetch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Marketplace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch, this is the rule to start with:
fetch 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 Marketplace, apply this rule, and every fetch call is checked against it from then on.
Questions about fetch
Get full detail on one published listing by its listing slug (not a contributor slug). Read-only, no authentication required (public endpoint, IP rate-limited). Returns title, description, short_description, product_story, included_components, use_cases, industry_focus, complexity_level, listing_type, product_formats, thumbnail_url, an array of pricing tiers (name, price_cents, setup_fee_cents, description, billing_interval, features), a contributor object (slug, display_name, badge_tier, bio, credential_summary, credential_badges), and a category object (name, slug). Use after search or list_categories to drill into a specific result. It is categorised as a Read tool in the Marketplace MCP Server, which means it retrieves data without modifying state.
fetch accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Marketplace MCP server in PolicyLayer and add a rule for fetch: 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 Marketplace. Nothing to install.
fetch 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 fetch 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 fetch. 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.
fetch is provided by the Marketplace MCP server (https://gallandigital.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Marketplace, and thousands of servers like it.
This server
Across the catalogue