get_workspace_info

THE RISK

Low Risk

Why get_workspace_info needs a policy

This tool queries and returns workspace configuration state—the root directory path and available MCP server listings. It retrieves information without side effects, making it a Read operation.

From the tool's definition Tool name 'get_workspace_info' and description 'Get the currently configured workspace root directory and available MCP servers' indicate retrieval of configuration metadata with no modification, deletion, or execution of external operations.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access get_workspace_info gives an agent:

POLICY

How to control get_workspace_info

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 get_workspace_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspace_info": {}
  }
}

get_workspace_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Bc Code Intelligence — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bc Code Intelligence tools

Destructive workflow_cancel Cancel a workflow session or clear all workflow sessions. Use cases: - Cancel a stale/orp Execute workflow_batch Apply batch operations to multiple pattern instances in a Workflow Engine v2 session. For Execute workflow_start Start a workflow session - a stateful checklist management system that drives agents throu Execute reload_layers Reload layers after configuration changes without restarting MCP server. Useful for testin Write create_layer_content Create a new topic, specialist, or prompt in a BC Code Intelligence layer with proper fron Write scaffold_layer_repo Create BC Code Intelligence layer folder structure with templates. Use this to bootstrap a Write set_workspace_info Set workspace root directory and available MCP server IDs. Enables project-specific knowle Write workflow_complete Complete a Workflow Engine v2 session and generate the final report. Call this when all f

All 27 Bc Code Intelligence tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_workspace_info

What does the get_workspace_info tool do? +

Get the currently configured workspace root directory and available MCP servers, if any. It is categorised as a Read tool in the Bc Code Intelligence MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspace_info? +

Register the Bc Code Intelligence MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_workspace_info? +

get_workspace_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspace_info? +

Yes. Add a rate_limit block to the get_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.

How do I block get_workspace_info completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_workspace_info? +

get_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.

Enforce policy on every Bc Code Intelligence tool call.

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.

CHECK YOUR STACK →