List past qualitative (GRAIN) analyses. Optionally filter by portfolio_id.
AI agents call list_grain_analyses 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 retrieves historical analysis data with optional filtering by portfolio_id. It is a read-only operation that queries existing records without side effects, modifications, or external triggers. The low severity reflects minimal blast radius if misused—an AI agent could only retrieve analysis records it may already have access to.
From the tool's definition Tool name includes 'list' and description states 'List past qualitative (GRAIN) analyses' with optional filtering. No modifications, deletions, or external operations are performed.
Attacks that exploit this kind of access
List past qualitative (GRAIN) analyses. Optionally filter by portfolio_id. 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_grain_analyses: 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_grain_analyses 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_grain_analyses 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_grain_analyses. 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_grain_analyses 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 →