fetch_full_docs

Retrieve complete Shopify documentation

SERVERShopify Dev SOURCE@Shopify/dev-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity verified Pull the record →

This record as markdown: /tools/shopify/fetch-full-docs.md

WHAT IT DOES

What fetch_full_docs does on Shopify Dev

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

RISK

Why fetch_full_docs is rated Low

This tool only retrieves documentation—a passive information-gathering operation. No data is created, modified, deleted, or executed. The sibling tools (introspect_admin_schema, learn_shopify_api, search_docs_chunks, validate_*) confirm this is a documentation/reference server. Misuse risk is minimal since reading documentation cannot damage systems or data.

From the tool's definition Tool name 'fetch_full_docs' and description 'Retrieve complete Shopify documentation' indicate a read-only operation that queries/retrieves documentation data with no side effects or modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fetch_full_docs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Shopify Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_full_docs, this is the rule to start with:

fetch_full_docs Allowed

fetch_full_docs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_full_docs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Shopify Dev, apply this rule, and every fetch_full_docs call is checked against it from then on.

FAQ

Questions about fetch_full_docs

What does the fetch_full_docs tool do? +

Retrieve complete Shopify documentation. It is categorised as a Read tool in the Shopify Dev MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_full_docs? +

Register the Shopify Dev MCP server in PolicyLayer and add a rule for fetch_full_docs: 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 Shopify Dev. Nothing to install.

What risk level is fetch_full_docs? +

fetch_full_docs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_full_docs? +

Yes. Add a rate_limit block to the fetch_full_docs 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.

How do I block fetch_full_docs completely? +

Set action: deny in the PolicyLayer policy for fetch_full_docs. 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.

What MCP server provides fetch_full_docs? +

fetch_full_docs is provided by the Shopify Dev MCP server (@Shopify/dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Shopify Dev, and thousands of servers like it.

This server

All 6 Shopify Dev tools →

Across the catalogue

detect_slop_full on Slop Cop → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →