List dataset metadata keys derived from data/*.meta.json.
AI agents call list_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 performs a straightforward query operation to retrieve and list metadata keys from JSON files. It has no side effects—it does not create, modify, delete, or execute any operations.
From the tool's definition Tool name 'list_dataset_metadata' combined with description 'List dataset metadata keys derived from data/*.meta.json' indicates retrieval of metadata information without modification, deletion, or execution of arbitrary operations.
Attacks that exploit this kind of access
List dataset metadata keys derived from data/*.meta.json. 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 list_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.
list_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 list_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 list_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.
list_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 →