Low Risk

get_flow_context_status

Query the current status of a flow execution by its context ID.

How to control get_flow_context_status ↓

What get_flow_context_status does on Now Sdk Ext

AI agents call get_flow_context_status 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.

Low Risk

Why get_flow_context_status needs a policy

This tool queries and retrieves the execution status of a flow—a read-only operation that returns information without modifying, deleting, or executing anything. The verb 'Query' and 'get' are characteristic of Read operations. No data is created, modified, or destroyed, and no external processes are triggered by this query itself.

From the tool's definition Tool name 'get_flow_context_status' and description 'Query the current status of a flow execution by its context ID' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_flow_context_status gives an agent:

How to control get_flow_context_status

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_context_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_flow_context_status": {}
  }
}

get_flow_context_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Now Sdk Ext — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_flow_context_status

What does the get_flow_context_status tool do? +

Query the current status of a 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.

How do I enforce a policy on get_flow_context_status? +

Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for get_flow_context_status: 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.

What risk level is get_flow_context_status? +

get_flow_context_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_flow_context_status? +

Yes. Add a rate_limit block to the get_flow_context_status 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.

How do I block get_flow_context_status completely? +

Set action: deny in the PolicyLayer policy for get_flow_context_status. 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.

What MCP server provides get_flow_context_status? +

get_flow_context_status 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.

Enforce policy on every Now Sdk Ext tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.