Lists all available datacubes (coverages) in rasdaman.
AI agents call list_coverages to retrieve information from Rasdaman MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about available coverages without creating, modifying, deleting, or executing operations. It is a simple enumeration/listing operation typical of Read category tools. Low severity because listing available data poses minimal risk even if called inappropriately by an agent.
From the tool's definition Tool name 'list_coverages' and description 'Lists all available datacubes (coverages) in rasdaman' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_coverages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rasdaman MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_coverages:
{
"version": "1",
"default": "deny",
"tools": {
"list_coverages": {}
}
}list_coverages 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.
Lists all available datacubes (coverages) in rasdaman. It is categorised as a Read tool in the Rasdaman MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rasdaman MCP Server MCP server in PolicyLayer and add a rule for list_coverages: 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 Rasdaman MCP Server. Nothing to install.
list_coverages 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 list_coverages 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 list_coverages. 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.
list_coverages is provided by the Rasdaman MCP Server MCP server (rasdaman/rasdaman-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rasdaman 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.
4 Rasdaman MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.