Low Risk

list_locations

List all fulfillment locations (physical stores, warehouses, 3PLs). Use the returned IDs with adjust_inventory and create_fulfillment.

How to control list_locations ↓

What list_locations does on Mcp Ap2

AI agents call list_locations to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_locations needs a policy

This tool retrieves metadata about fulfillment locations and returns identifiers for use by other tools. It has no side effects, creates no resources, and does not modify any state. The severity is low because even if misused, listing location data has minimal blast radius compared to operations that could alter inventory or financial transactions.

From the tool's definition Tool description states 'List all fulfillment locations' — a retrieval operation with no modification of data. The verb 'list' and the context of returning location IDs for reference in other operations indicates a purely informational/read-only function.

Documented attack patterns abuse exactly the kind of access list_locations gives an agent:

How to control list_locations

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for list_locations:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_locations": {}
  }
}

list_locations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_locations

What does the list_locations tool do? +

List all fulfillment locations (physical stores, warehouses, 3PLs). Use the returned IDs with adjust_inventory and create_fulfillment. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_locations? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for list_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 Mcp Ap2. Nothing to install.

What risk level is list_locations? +

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

Can I rate-limit list_locations? +

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

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

list_locations is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.