cs_diagnostics
Return compile/analyzer diagnostics (errors, warnings) for a C# script. Opens the file and waits briefly for OmniSharp to publish.
This record as markdown: /tools/breakpoint-mcp/cs-diagnostics.md
What cs_diagnostics does on Breakpoint
AI agents call cs_diagnostics to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | C# script path |
wait_ms | integer | — | Max time to wait for the first publish (default 2000; OmniSharp's first analysis can be slow) |
Parameters from the server's own tool schema.
Why cs_diagnostics is rated Low
The tool reads and returns diagnostic information (errors, warnings) from a C# script using OmniSharp. It only retrieves data and has no side effects beyond opening a file for analysis.
From the tool's definition Return compile/analyzer diagnostics (errors, warnings) for a C# script. Opens the file and waits briefly for OmniSharp to publish.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs cs_diagnostics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cs_diagnostics, this is the rule to start with:
cs_diagnostics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every cs_diagnostics call is checked against it from then on.
Questions about cs_diagnostics
Return compile/analyzer diagnostics (errors, warnings) for a C# script. Opens the file and waits briefly for OmniSharp to publish. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
cs_diagnostics accepts 2 parameters: path, wait_ms. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for cs_diagnostics: 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 Breakpoint. Nothing to install.
cs_diagnostics 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 cs_diagnostics 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 cs_diagnostics. 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.
cs_diagnostics is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue