This record as markdown: /tools/io-github-dreamrec-livepilot/evaluate-with-fabric.md
What evaluate_with_fabric does on Livepilot
AI agents invoke evaluate_with_fabric to trigger actions in Livepilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why evaluate_with_fabric is rated High
The word 'evaluate' in the tool name suggests execution of some expression or code. 'Fabric' may refer to a framework or scripting system. Without a description, this is uncertain, but 'evaluate' tools typically run code or expressions, warranting an Execute classification. Confidence is lowered due to the empty description.
From the tool's definition Tool name contains 'evaluate' which strongly suggests code/expression evaluation; description is empty providing no further clarification
Attacks that exploit this kind of access
The rule that runs evaluate_with_fabric safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For evaluate_with_fabric, this is the rule to start with:
evaluate_with_fabric stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every evaluate_with_fabric call is checked against it from then on.
Questions about evaluate_with_fabric
evaluate_with_fabric is a execute tool on the Livepilot MCP server. It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Livepilot MCP server in PolicyLayer and add a rule for evaluate_with_fabric: 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 Livepilot. Nothing to install.
evaluate_with_fabric is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the evaluate_with_fabric 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 evaluate_with_fabric. 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.
evaluate_with_fabric is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
Across the catalogue