Set workspace root directory and available MCP server IDs. Enables project-specific knowledge layers and ecosystem-aware specialist recommendations. Call before other BC tools to activate workspace context.
AI agents use set_workspace_info to create or update resources in Bc Code Intelligence — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bc Code Intelligence environment.
This tool writes/sets configuration data (workspace root directory and MCP server IDs) in a reversible manner. It changes application state but does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misconfiguration could lead to tools operating on wrong directories or with incorrect context, potentially affecting code analysis or modification operations downstream.
From the tool's definition Tool name 'set_workspace_info' and description states it 'Set workspace root directory and available MCP server IDs' — this modifies workspace configuration state that affects how other tools operate.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access set_workspace_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bc Code Intelligence, and nothing reaches the server without passing your rules. This is the rule we recommend for set_workspace_info:
{
"version": "1",
"default": "deny",
"tools": {
"set_workspace_info": {
"limits": [
{
"counter": "set_workspace_info_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_workspace_info 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.
Set workspace root directory and available MCP server IDs. Enables project-specific knowledge layers and ecosystem-aware specialist recommendations. Call before other BC tools to activate workspace context. It is categorised as a Write tool in the Bc Code Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bc Code Intelligence MCP server in PolicyLayer and add a rule for set_workspace_info: 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 Bc Code Intelligence. Nothing to install.
set_workspace_info 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 set_workspace_info 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 set_workspace_info. 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.
set_workspace_info is provided by the Bc Code Intelligence MCP server (jeremyvyska/bc-code-intelligence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bc Code Intelligence, 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.
27 Bc Code Intelligence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.