cs_signature_help
Show the call signature(s) and active parameter at a position (the parameter hints an IDE pops up inside a call).
This record as markdown: /tools/breakpoint-mcp/cs-signature-help.md
What cs_signature_help does on Breakpoint
AI agents call cs_signature_help 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_signature_help is rated Low
This tool retrieves and displays IDE-style parameter hints for code completion—a read-only operation with no side effects. It queries signature information but does not execute code, modify state, or perform any destructive action. The low severity reflects the minimal risk of misuse; an AI agent accessing this tool can only view metadata about function signatures.
From the tool's definition Tool name 'cs_signature_help' and description 'Show the call signature(s) and active parameter at a position' indicate retrieval and display of metadata about function signatures. No data modification, deletion, or code execution occurs.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs cs_signature_help 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_signature_help, this is the rule to start with:
cs_signature_help 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_signature_help call is checked against it from then on.
Questions about cs_signature_help
Show the call signature(s) and active parameter at a position (the parameter hints an IDE pops up inside a call). It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
cs_signature_help 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_signature_help: 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_signature_help 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_signature_help 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_signature_help. 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_signature_help 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