Return dataset metadata for the given key (see list_dataset_metadata).
AI agents call get_dataset_metadata to retrieve information from Aurora-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata about datasets with no side effects or modifications. It performs a lookup operation based on a provided key, consistent with the Read category for data retrieval tools. The narrow scope (metadata only, not data manipulation) and lack of any modification, execution, or destructive capability warrant low severity.
From the tool's definition Tool description states it 'Return[s] dataset metadata' which is a retrieval operation. The name 'get_dataset_metadata' and sibling tools like 'list_dataset_metadata', 'get_glossary', 'read_text' confirm this is a read-only query tool.
Attacks that exploit this kind of access
Return dataset metadata for the given key (see list_dataset_metadata). It is categorised as a Read tool in the Aurora-MCP MCP Server, which means it retrieves data without modifying state.
Register the Aurora- MCP server in PolicyLayer and add a rule for get_dataset_metadata: 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 Aurora-MCP. Nothing to install.
get_dataset_metadata 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_metadata 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_metadata. 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_metadata is provided by the Aurora- MCP server (ndaniel/aurora-mcp). 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 →