List all systematic trading rules attached to a portfolio, including their trigger/action definitions, active status, and priority order.
AI agents call list_rules to retrieve information from Sablier MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing rule configuration data from a portfolio. It performs inspection/audit of trading rules without creating, modifying, deleting, or triggering any trades or financial transactions. No code execution, resource modification, or financial commitment occurs.
From the tool's definition Tool description explicitly states 'List all systematic trading rules' — a retrieval operation with no side effects. Returns rule metadata (definitions, status, priority) but does not modify, delete, or execute trading actions.
Attacks that exploit this kind of access
List all systematic trading rules attached to a portfolio, including their trigger/action definitions, active status, and priority order. It is categorised as a Read tool in the Sablier MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for list_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.
list_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_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 →