cs_hover
Hover documentation/type info at a position (e.g. the Counter : int type).
This record as markdown: /tools/breakpoint-mcp/cs-hover.md
What cs_hover does on Breakpoint
AI agents call cs_hover 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 |
|---|---|---|---|
line | integer | Yes | 0-based line |
path | string | Yes | C# script path (res://..., absolute, or relative to the C# project root) |
character | integer | Yes | 0-based character |
Parameters from the server's own tool schema.
Why cs_hover is rated Low
This tool retrieves documentation and type information at a given code position, similar to an IDE hover feature. It only reads/queries metadata and has no side effects.
From the tool's definition Hover documentation/type info at a position
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs cs_hover 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_hover, this is the rule to start with:
cs_hover 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_hover call is checked against it from then on.
Questions about cs_hover
Hover documentation/type info at a position (e.g. the Counter : int type). It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
cs_hover accepts 3 parameters: line, path, character. Required: line, path, character. 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_hover: 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_hover 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_hover 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_hover. 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_hover 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