libi.compute_object_track_providers
OPTIONAL PAID mask refinement via fal.ai SAM2. NOT the default tracker — use
This record as markdown: /tools/libi/libi.compute-object-track-providers.md
What libi.compute_object_track_providers does on Libi
AI agents use libi.compute_object_track_providers to commit financial operations through Libi, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why libi.compute_object_track_providers is rated Critical
Tool triggers a paid external API call, incurring financial cost when used.
From the tool's definition OPTIONAL PAID mask refinement via fal.ai SAM2
Attacks that exploit this kind of access
The rule that runs libi.compute_object_track_providers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.compute_object_track_providers, this is the rule to start with:
Any call to libi.compute_object_track_providers is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Libi, apply this rule, and every libi.compute_object_track_providers call is checked against it from then on.
Questions about libi.compute_object_track_providers
OPTIONAL PAID mask refinement via fal.ai SAM2. NOT the default tracker — use. It is categorised as a Financial tool in the Libi MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Libi MCP server in PolicyLayer and add a rule for libi.compute_object_track_providers: 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 Libi. Nothing to install.
libi.compute_object_track_providers is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the libi.compute_object_track_providers 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 libi.compute_object_track_providers. 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.
libi.compute_object_track_providers is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Libi, and thousands of servers like it.
Across the catalogue