AI agents call get_conformance 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.
This tool returns conformance information (e.g., which API standards the STAC server implements), which is a pure retrieval operation with no side effects, data modification, code execution, or destructive capability. It is informational in nature and consistent with other Read-category tools on the server like get_root, get_collection, and get_item.
From the tool's definition Tool name 'get_conformance' and description 'Return server conformance classes' indicate a read-only query operation that retrieves metadata about server capabilities without modifying data.
Documented attack patterns abuse exactly the kind of access get_conformance gives an agent:
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_conformance:
{
"version": "1",
"default": "deny",
"tools": {
"get_conformance": {}
}
}get_conformance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return server conformance classes. It is categorised as a Read tool in the STAC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the STAC MCP Server MCP server in PolicyLayer and add a rule for get_conformance: 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.
get_conformance 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_conformance 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_conformance. 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_conformance 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.
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.