check_flow_job
AI agents call check_flow_job 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 name 'check_flow_job' most naturally maps to a status-check operation, which is a read action that retrieves information about an existing job without modifying state. However, confidence is moderate due to the empty description. The sibling tools on this server include analysis and computation tools that are clearly Read operations, and this tool appears consistent with that pattern.
From the tool's definition Tool name 'check_flow_job' suggests checking or querying the status of a flow/job. The naming pattern aligns with other read-like operations on the server (analyze_*, compute_*). No description provided to confirm.
Attacks that exploit this kind of access
check_flow_job. 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 check_flow_job: 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.
check_flow_job 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 check_flow_job 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 check_flow_job. 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.
check_flow_job 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 →