get_locations

Fetch store locations

SERVERShopify Graphql SOURCEuvu-store/shopify-graphql-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/uvu-store-shopify-graphql-mcp/get-locations.md

WHAT IT DOES

What get_locations does on Shopify Graphql

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

RISK

Why get_locations is rated Low

This tool retrieves location data from a Shopify store without creating, modifying, deleting, or executing any actions. It is a straightforward read-only query operation that poses minimal risk even if misused by an AI agent, as it only exposes existing business location information.

From the tool's definition Tool name 'get_locations' and description 'Fetch store locations' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_locations safely

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

get_locations Allowed

get_locations 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": {
    "get_locations": {}
  }
}

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

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

FAQ

Questions about get_locations

What does the get_locations tool do? +

Fetch store locations. It is categorised as a Read tool in the Shopify Graphql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_locations? +

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

What risk level is get_locations? +

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

Can I rate-limit get_locations? +

Yes. Add a rate_limit block to the get_locations 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 get_locations completely? +

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

get_locations is provided by the Shopify Graphql MCP server (uvu-store/shopify-graphql-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 Graphql, and thousands of servers like it.

This server

All 319 Shopify Graphql tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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