Return signature help for the active call at a zero-based LSP position.
AI agents call lsp_signature_help to retrieve information from Syntax Map without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries symbol signatures without side effects. It provides code intelligence similar to IDE hover/autocomplete features. The broader server enables code analysis, indexing, and lookups—all read-only operations. There is no capability to modify, delete, or execute code, making this a low-severity Read category tool.
From the tool's definition Tool returns signature help for code analysis at an LSP position. No modifications, deletions, or execution of code occur—it only retrieves and displays function/method signature information for IDE-like assistance.
Attacks that exploit this kind of access
Return signature help for the active call at a zero-based LSP position. It is categorised as a Read tool in the Syntax Map MCP Server, which means it retrieves data without modifying state.
Register the Syntax Map MCP server in PolicyLayer and add a rule for lsp_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 Syntax Map. Nothing to install.
lsp_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 lsp_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 lsp_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.
lsp_signature_help is provided by the Syntax Map MCP server (kht6163/syntax-map-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →