Medium Risk

il_circle_detector_set_max_count

设置圆定位工具所使用的最大检出个数,并返回设置完成的圆定位工具的功能调用的对象。 返回结构是一个序列化的JSON字符串,属性包括: LpvClassName(调用工具函数的名称) 和 InputParameterFile(调用工具函数需要传入的参数文件名称)。这两个属性的值可以从前处理的MCP工具的返回值中获取。LpvClassName 表示圆定位工具的功能调用的对象名称,目前名称应为:ILCircleDetector (圆定位工具的功能相关对象); InputParameterFile 表示圆定位工具的功能调用的对象的参数文件名称。

Part of the Leaper Vision Toolkit MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use il_circle_detector_set_max_count to create or modify resources in Leaper Vision Toolkit. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call il_circle_detector_set_max_count repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Leaper Vision Toolkit.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

leaper-mcp-leaper-mcp-proxy.yaml
tools:
  il_circle_detector_set_max_count:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Leaper Vision Toolkit policy for all 169 tools.

Tool Name il_circle_detector_set_max_count
Category Write
Risk Level Medium

View all 169 tools →

What does the il_circle_detector_set_max_count tool do? +

设置圆定位工具所使用的最大检出个数,并返回设置完成的圆定位工具的功能调用的对象。 返回结构是一个序列化的JSON字符串,属性包括: LpvClassName(调用工具函数的名称) 和 InputParameterFile(调用工具函数需要传入的参数文件名称)。这两个属性的值可以从前处理的MCP工具的返回值中获取。LpvClassName 表示圆定位工具的功能调用的对象名称,目前名称应为:ILCircleDetector (圆定位工具的功能相关对象); 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.

How do I enforce a policy on il_circle_detector_set_max_count? +

Add a rule in your Intercept YAML policy under the tools section for il_circle_detector_set_max_count. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Leaper Vision Toolkit MCP server.

What risk level is il_circle_detector_set_max_count? +

il_circle_detector_set_max_count is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit il_circle_detector_set_max_count? +

Yes. Add a rate_limit block to the il_circle_detector_set_max_count rule in your Intercept 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.

How do I block il_circle_detector_set_max_count completely? +

Set action: deny in the Intercept policy for il_circle_detector_set_max_count. 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.

What MCP server provides il_circle_detector_set_max_count? +

il_circle_detector_set_max_count is provided by the Leaper Vision Toolkit MCP server (leaper-mcp/leaper-mcp-proxy). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Leaper Vision Toolkit

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.