Validate multiple file paths in a BIDS dataset. This tool checks a batch of file paths for BIDS compliance. Use this when validating an entire dataset structure or multiple files at once. Args: paths: List of file paths to validate (each must be relative to BIDS dataset root, starting with '/') R...
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Part of the Neuro server.
Free to start. No card required.
AI agents call validate_bids_dataset to retrieve information from Neuro without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though validate_bids_dataset only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"validate_bids_dataset": {}
}
}See the full Neuro policy for all 34 tools.
These attack patterns abuse exactly the kind of access validate_bids_dataset gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Validate multiple file paths in a BIDS dataset. This tool checks a batch of file paths for BIDS compliance. Use this when validating an entire dataset structure or multiple files at once. Args: paths: List of file paths to validate (each must be relative to BIDS dataset root, starting with '/') Returns: Validation summary with overall compliance and per-file results Examples: - validate_bids_dataset(['/sub-01/anat/sub-01_T1w.nii.gz', '/participants.tsv']). It is categorised as a Read tool in the Neuro MCP Server, which means it retrieves data without modifying state.
Register the Neuro MCP server in PolicyLayer and add a rule for validate_bids_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 Neuro. Nothing to install.
validate_bids_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 validate_bids_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 validate_bids_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.
validate_bids_dataset is provided by the Neuro MCP server (@brain-bbqs/neuro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 34 Neuro tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.