设置直线定位工具所使用的检测的搜索策略，并返回设置完成的直线定位工具的功能调用的对象。 返回结构是一个序列化的JSON字符串，属性包括： LpvClassName(调用工具函数的名称) 和 InputParameterFile(调用工具函数需要传入的参数文件名称)。这两个属性的值可以从前处理的MCP工具的返回值中获取。LpvClassName 表示直线定位工具的功能调用的对象名称，目前名称应为：ILLineDetector (直线定位工具的功能相关对象); InputParameterFile 表示直线定位工具的功能调用的对象的参数文件名称。
AI agents use il_line_detector_set_find_by to create or update resources in Leaper Vision Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Leaper Vision Toolkit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
findBy | string | — | 检测的搜索策略，传入类型为 LPVFindBy 类型。指的是如何从区域中的多条符合条件的候选直线中选取结果。有效的类型为：LPVFindBest（选择一个或多个最高分。）、LPVFindFirst（沿着区域的扫描方向，选择第一个或前几个。）、LPVFindLast（沿着区域的扫描方向，选择最后一个或后几个。）、LPVF |
InputParameterFile | string | — | 指定的 ILLineDetector 类的文件地址，调用工具函数需要传入的参数文件名称。在调用此工具前要保证前处理中一定要有且仅有一次的 ILLineDetector 初始化工具调用。这个属性的值需要从前处理的MCP工具的返回值 InputParameterFile 字段中获取。 |
Parameters from the server's own tool schema.
This tool creates or modifies configuration parameters for the line detector—it sets detection strategies and returns a configured functional object. This is a Write operation (configuration modification) rather than Read (which would only query existing settings) or Execute (which would trigger the actual detection).
From the tool's definition Tool name 'il_line_detector_set_find_by' and description indicate it 'sets' (设置) the detection search strategy for a line detection tool and 'returns' a configured object with serialized JSON containing LpvClassName and InputParameterFile.
Attacks that exploit this kind of access
设置直线定位工具所使用的检测的搜索策略，并返回设置完成的直线定位工具的功能调用的对象。 返回结构是一个序列化的JSON字符串，属性包括： LpvClassName(调用工具函数的名称) 和 InputParameterFile(调用工具函数需要传入的参数文件名称)。这两个属性的值可以从前处理的MCP工具的返回值中获取。LpvClassName 表示直线定位工具的功能调用的对象名称，目前名称应为：ILLineDetector (直线定位工具的功能相关对象); InputParameterFile 表示直线定位工具的功能调用的对象的参数文件名称。. It is categorised as a Write tool in the Leaper Vision Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
il_line_detector_set_find_by accepts 2 parameters: findBy, InputParameterFile. The full parameter table on this page comes from the server's own tool schema.
Register the Leaper Vision Toolkit MCP server in PolicyLayer and add a rule for il_line_detector_set_find_by: 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 Leaper Vision Toolkit. Nothing to install.
il_line_detector_set_find_by 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 il_line_detector_set_find_by 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 il_line_detector_set_find_by. 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.
il_line_detector_set_find_by is provided by the Leaper Vision Toolkit MCP server (leaper-mcp/leaper-mcp-proxy). 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 →