generate_dbt_profile
AI agents use generate_dbt_profile to create or update resources in Fabric Dw Mcp Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fabric Dw Mcp Cli environment.
The tool creates (generates) configuration data for dbt, which is reversible—a generated profile can be deleted or regenerated. This places it in the Write category rather than Read (which would be retrieval only) or Execute (which would run arbitrary code).
From the tool's definition Tool name 'generate_dbt_profile' suggests generation of a dbt (data build tool) profile configuration file. dbt profiles are used to configure database connections and credentials. Generating such a profile would create or modify configuration data.
Attacks that exploit this kind of access
generate_dbt_profile. It is categorised as a Write tool in the Fabric Dw Mcp Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fabric Dw Mcp Cli MCP server in PolicyLayer and add a rule for generate_dbt_profile: 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 Fabric Dw Mcp Cli. Nothing to install.
generate_dbt_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_dbt_profile 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 generate_dbt_profile. 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.
generate_dbt_profile is provided by the Fabric Dw Mcp Cli MCP server (sdebruyn/fabric-dw-mcp-cli). 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 →