List available datasets in the loaded FDS results.
AI agents call bulc_list_result_datasets to retrieve information from BULC Building Designer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing result datasets from an FDS (Fire Dynamics Simulator) file without modifying, executing, or deleting any data. It is a purely informational query operation, making it a Read category tool with low severity since misuse would only expose data already present in the loaded simulation file.
From the tool's definition Tool name contains 'list' and description states 'List available datasets in the loaded FDS results' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
List available datasets in the loaded FDS results. It is categorised as a Read tool in the BULC Building Designer MCP Server, which means it retrieves data without modifying state.
Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_list_result_datasets: 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 BULC Building Designer. Nothing to install.
bulc_list_result_datasets 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 bulc_list_result_datasets 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 bulc_list_result_datasets. 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.
bulc_list_result_datasets is provided by the BULC Building Designer MCP server (using76/bulc_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 →