get_variable_standard_names
AI agents call get_variable_standard_names to retrieve information from Erddap Mcp Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to fetch standard variable names or metadata from ERDDAP, which is a retrieval operation with no side effects. No description is provided, which moderately reduces confidence, but the naming pattern and context of sibling tools strongly suggest this is a metadata/data Read operation. No execution, modification, deletion, or financial impact is indicated.
From the tool's definition Tool name 'get_variable_standard_names' indicates retrieval of variable naming information from ERDDAP metadata. Sibling tools (list_dataset_variables, list_datasets, search_datasets, get_dataset_variable_data) are all Read operations.
Attacks that exploit this kind of access
get_variable_standard_names. It is categorised as a Read tool in the Erddap Mcp Demo MCP Server, which means it retrieves data without modifying state.
Register the Erddap Mcp Demo MCP server in PolicyLayer and add a rule for get_variable_standard_names: 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 Demo. Nothing to install.
get_variable_standard_names 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_variable_standard_names 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_variable_standard_names. 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_variable_standard_names is provided by the Erddap Mcp Demo MCP server (srstsavage/erddap-mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →