Retrieve the error message from a failed flow execution by its context ID.
AI agents call get_flow_error to retrieve information from Now Sdk Ext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve error messages from completed flow executions. It does not create, modify, delete, or execute any operations—it simply retrieves diagnostic information. The blast radius is minimal as misuse would only expose error details already generated by past executions. This is a pure Read operation.
From the tool's definition Tool name 'get_flow_error' and description 'Retrieve the error message from a failed flow execution by its context ID' indicate a retrieval operation that queries existing error data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_flow_error gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flow_error:
{
"version": "1",
"default": "deny",
"tools": {
"get_flow_error": {}
}
}get_flow_error is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the error message from a failed flow execution by its context ID. It is categorised as a Read tool in the Now Sdk Ext MCP Server, which means it retrieves data without modifying state.
Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for get_flow_error: 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 Now Sdk Ext. Nothing to install.
get_flow_error 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_error 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_error. 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_error is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.