AI agents use export_bc3_budget to create or update resources in Bonsai-mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bonsai-mcp environment.
The tool appears to export budget data, which constitutes data creation/generation rather than destructive deletion. Without a description, confidence is reduced, but the export pattern on this Blender/IFC server suggests it produces output files or structured data (Write category). It's not Destructive because exports typically do not irreversibly delete source data.
From the tool's definition Tool name 'export_bc3_budget' indicates creation/export of budget data in BC3 format (a standard construction cost format). Despite empty description, the 'export' verb combined with 'budget' in name suggests generating and writing structured data output.
Documented attack patterns abuse exactly the kind of access export_bc3_budget gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bonsai-mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for export_bc3_budget:
{
"version": "1",
"default": "deny",
"tools": {
"export_bc3_budget": {
"limits": [
{
"counter": "export_bc3_budget_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_bc3_budget stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
export_bc3_budget. It is categorised as a Write tool in the Bonsai-mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bonsai- MCP server in PolicyLayer and add a rule for export_bc3_budget: 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 Bonsai-mcp. Nothing to install.
export_bc3_budget 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 export_bc3_budget 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 export_bc3_budget. 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.
export_bc3_budget is provided by the Bonsai- MCP server (jotaderodriguez/bonsai_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bonsai-mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Bonsai-mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.