Get details of a single location by its ID.
AI agents call get_location to retrieve information from Kockatoos Shopify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation ('Get details') without any capability to modify, delete, or execute operations. It is a simple query that returns information about a location, making it a Read category tool. The severity is low because even if misused, retrieving location details has minimal blast radius and no financial or destructive impact.
From the tool's definition Tool name is 'get_location' and description states it retrieves details of a single location by ID with no modification or side effects indicated.
Attacks that exploit this kind of access
Get details of a single location by its ID. It is categorised as a Read tool in the Kockatoos Shopify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kockatoos Shopify MCP Server MCP server in PolicyLayer and add a rule for get_location: 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 Kockatoos Shopify MCP Server. Nothing to install.
get_location 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 get_location 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 get_location. 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.
get_location is provided by the Kockatoos Shopify MCP Server MCP server (untitled-developers/shopify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →