evaluate_rules
AI agents invoke evaluate_rules to trigger actions in Sablier MCP Server. 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.
The description is empty, which significantly lowers confidence. Based on the tool name 'evaluate_rules' and the context of sibling tools like 'backtest_rules', this likely executes rule logic against portfolio or market data. 'Evaluate' implies computation/execution rather than simple data retrieval or modification. Without more detail, Execute is the most plausible category, but confidence is low.
From the tool's definition Tool name 'evaluate_rules' with empty description; sibling tools include 'backtest_rules' and 'analyze_*' functions suggesting rule evaluation/execution logic
Attacks that exploit this kind of access
evaluate_rules. It is categorised as a Execute tool in the Sablier MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for evaluate_rules: 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 Sablier MCP Server. Nothing to install.
evaluate_rules 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_rules 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_rules. 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_rules is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-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 →