Low Risk

list_registries

list_registries

How to control list_registries ↓

What list_registries does on Amazon Location Service MCP Server

AI agents call list_registries to retrieve information from Amazon Location Service MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_registries needs a policy

The 'list_' prefix is a strong signal for a Read operation that retrieves information about registries. Given the AWS Location Service context and the absence of mutation keywords (create, update, delete, execute), this is classified as Read with low severity since listing registries is a basic query operation with no destructive potential.

From the tool's definition Tool name 'list_registries' indicates a listing/retrieval operation. No description provided, but the pattern matches standard read operations like 'list' which query and return data without side effects.

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

How to control list_registries

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Location Service MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_registries:

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

list_registries 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 Amazon Location Service MCP Server — 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_registries

What does the list_registries tool do? +

list_registries. It is categorised as a Read tool in the Amazon Location Service MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_registries? +

Register the Amazon Location Service MCP Server MCP server in PolicyLayer and add a rule for list_registries: 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 Amazon Location Service MCP Server. Nothing to install.

What risk level is list_registries? +

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

Can I rate-limit list_registries? +

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

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

list_registries is provided by the Amazon Location Service MCP Server MCP server (awslabs.aws-location-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Location Service MCP Server tool call.

Start from Amazon Location Service MCP Server, 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.

805 Amazon Location Service MCP Server 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.