Low Risk

get_queryables

Get the queryable properties for a specific STAC collection by its ID.

How to control get_queryables ↓

What get_queryables does on STAC MCP Server

AI agents call get_queryables to retrieve information from STAC 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 get_queryables needs a policy

This tool retrieves schema/metadata information about a STAC collection's queryable properties. It is a read-only operation with no side effects, no data modification, and no code execution. The blast radius is minimal—at worst, an AI agent could learn what properties exist in a collection, which is informational and non-damaging.

From the tool's definition Tool name 'get_queryables' and description 'Get the queryable properties for a specific STAC collection' indicate a retrieval operation.

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

How to control get_queryables

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

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

get_queryables 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 STAC 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 get_queryables

What does the get_queryables tool do? +

Get the queryable properties for a specific STAC collection by its ID. It is categorised as a Read tool in the STAC MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_queryables? +

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

What risk level is get_queryables? +

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

Can I rate-limit get_queryables? +

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

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

get_queryables is provided by the STAC MCP Server MCP server (wayfinder-foundry/stac-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every STAC MCP Server tool call.

Start from STAC 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.

10 STAC 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.