Validate FDS configuration for errors and warnings.
AI agents call bulc_validate_fds 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.
Validation tools inspect existing state and return diagnostic results without modifying, executing external systems, or deleting data. The tool reads FDS configuration state to identify errors or warnings, a pure read operation. The fire simulation context (BULC) and integration with design tools do not change this classification—validation alone is non-destructive and produces no side effects.
From the tool's definition Tool name 'bulc_validate_fds' and description 'Validate FDS configuration for errors and warnings' indicate checking/validation logic with no side effects.
Attacks that exploit this kind of access
Validate FDS configuration for errors and warnings. 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_validate_fds: 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_validate_fds 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_validate_fds 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_validate_fds. 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_validate_fds 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 →