This record as markdown: /tools/kh0pper-crow/get-dataset.md
What get_dataset does on Crow
AI agents call get_dataset to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dataset is rated Low
This tool retrieves data by ID without side effects. It performs a simple read operation consistent with querying or fetching data, placing it in the Read category with low severity since it does not alter state, delete data, or execute arbitrary operations.
From the tool's definition Tool name 'get_dataset' and description 'Retrieve a specific dataset by ID' indicate a query/fetch operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs get_dataset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dataset, this is the rule to start with:
get_dataset is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every get_dataset call is checked against it from then on.
Questions about get_dataset
Retrieve a specific dataset by ID. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for get_dataset: 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 Crow. Nothing to install.
get_dataset 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 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. 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 is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue