Get detailed information about a specific flow
AI agents call get_flow_details to retrieve information from GASSAPI 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 and queries flow metadata without executing, modifying, or deleting any flows. It is a straightforward read operation that returns information about an existing flow, presenting no side effects or risk of unintended consequences.
From the tool's definition Tool name 'get_flow_details' and description 'Get detailed information about a specific flow' indicate a data retrieval operation with no modification or execution of workflows.
Attacks that exploit this kind of access
Get detailed information about a specific flow. It is categorised as a Read tool in the GASSAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GASSAPI MCP Server MCP server in PolicyLayer and add a rule for get_flow_details: 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 GASSAPI MCP Server. Nothing to install.
get_flow_details 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 get_flow_details 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 get_flow_details. 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.
get_flow_details is provided by the GASSAPI MCP Server MCP server (martin-1103/mcp2). 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 →