list_feature_sets
AI agents call list_feature_sets 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.
The tool appears to retrieve or query available feature sets without modifying, executing, or deleting data. The 'list' verb strongly suggests a read-only operation. Although the description is empty, the context (financial analysis server with portfolio/scenario tools) and sibling tool names (analyze_*, check_*, compute_*) support classifying this as a simple data retrieval function.
From the tool's definition Tool name 'list_feature_sets' indicates a listing/retrieval operation with no side effects; the empty description prevents confirmation of specific functionality, but the naming pattern is consistent with Read category tools (list, get, fetch).
Attacks that exploit this kind of access
list_feature_sets. 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_feature_sets: 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_feature_sets 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_feature_sets 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_feature_sets. 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_feature_sets 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 →