Get detailed metadata information about a specific dataset
AI agents call get_dataset_info to retrieve information from ERDDAP 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 dataset metadata without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function analogous to GET requests in REST APIs. The low severity reflects minimal blast radius—an AI agent cannot cause harm by requesting dataset information.
From the tool's definition Tool retrieves 'detailed metadata information about a specific dataset' with no indication of modification or side effects. The verb 'Get' and the read-only nature of metadata retrieval establish this as a data query operation.
Documented attack patterns abuse exactly the kind of access get_dataset_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ERDDAP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dataset_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_dataset_info": {}
}
}get_dataset_info 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.
Get detailed metadata information about a specific dataset. It is categorised as a Read tool in the ERDDAP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ERDDAP MCP Server MCP server in PolicyLayer and add a rule for get_dataset_info: 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 ERDDAP MCP Server. Nothing to install.
get_dataset_info 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_dataset_info 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_dataset_info. 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_dataset_info is provided by the ERDDAP MCP Server MCP server (robertdcurrier/erddap2mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ERDDAP 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 ERDDAP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.