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 use cs_hover to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| 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 Medium
An AI agent can call cs_hover faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.
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 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.
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 Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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